User Experience Tradeoffs
You'll learn how navigation patterns, gestures, and platform-specific UI conventions differ between PWAs and native apps—and why matching user expectations matters.
The Core Challenge
Progressive Web Apps live in a hybrid world: they're web apps that feel like native apps, but they run in a browser context. This creates inevitable UX friction because users carry deeply ingrained expectations based on their platform (iOS, Android, desktop).
Navigation patterns differ significantly. Native apps typically use platform-specific navigation bars (iOS: bottom tab bar; Android: navigation drawer or bottom nav). PWAs must implement these in HTML/CSS, but browser chrome still appears. The back button behaves differently—native apps might show in-app navigation history, while PWAs navigate through browser history, potentially leaving your app entirely.
Gestures are another minefield. Native iOS apps expect swipe-from-edge for back navigation. Your PWA can implement custom swipe handlers, but they'll compete with browser gestures. Pull-to-refresh works differently across platforms, and some browsers override it entirely.
Platform UI expectations run deep. iOS users expect large header titles, specific animation curves, and standard system colors. Android users expect Material Design patterns, FABs, and different spacing. Desktop users expect keyboard shortcuts, hover states, and window controls. Your PWA can't perfectly replicate all these without massive conditional styling.
The Tradeoff Reality
You'll constantly balance: write-once consistency vs. platform-native feel. Over-customizing creates maintenance headaches. Under-customizing feels "off-brand" for the platform. Most successful PWAs pick a web-first identity with subtle platform accommodations (safe zones, gesture awareness, adaptive layouts).
Key Takeaway: PWAs trade pixel-perfect native UX for cross-platform reach and simplified distribution—success means embracing web patterns while respecting platform conventions where they matter most.