The Future of Cross-Platform User Interfaces
summary
Claim: product teams must invest in cross‑platform architecture now because platforms multiply faster than teams can staff. Implementation details: reuse web/JavaScript/HTML5 where possible, use React Native or hybrid shells like Electron and Ionic for platform parity, and only dip into native SDKs when necessary. Evidence: Safari on iPad exposes keyboard shortcuts when a Bluetooth keyboard is attached, Oculus expects eye‑tracking by 2022, and local iOS contractor rates run about $100–$150/hr, so native-first wastes budget and time.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:16Building consistent user experiences across multiple platforms has been a difficult job for decades.
- 2:11Microsoft Office in 2019
- 5:10Desktop Computers
- 6:56Laptop Computers
- 9:14Cellphones
- 11:04Smart Phones
- 14:42Tablets
- 19:39Touch-Screen Laptops
- 23:20Wearables
- 26:19Extended Reality
- 29:59Open Questions
related talks
30mIs a new Cross-platform Development Era coming
36mCross-platform DS in React Native: Musixmatch’s case study
36mCross Platform with React Native
56mDoes the Browser have a Future?
27mBuilding Cross Platform Desktop Apps With Electron
21mMaking Your Mobile Cross-Platform Dreams Come True with Modern Web
01h 14mHow to Build a Cross-Platform Design System in React
39mDoes The Browser Have A Future