Web Development
PWA
Native Apps
iOS17
Flutter
Blog AI Assistant
Ask anything about this article
Hi! I've read this article.
What would you like to know?
Ask anything about this article
Hi! I've read this article.
What would you like to know?
@farhan
In June 2026 Apple released iOS 17 with full support for Service Workers, background sync, and push notifications for Progressive Web Apps. After years of half‑measures, the web platform on iPhone now matches Android's capabilities. The impact is immediate:
"The web finally became a first‑class citizen on the most popular mobile OS," wrote @dan_abramov on X.
Developers are now debating a new question: Should we still invest in native SDKs for a product that can be shipped as a PWA and reach 100% of mobile users? The answer is nuanced, but the balance is shifting.
Three camps dominate the conversation:
All three promise "write once, run everywhere," yet they differ dramatically in performance, developer experience, and long‑term maintenance. Below is a side‑by‑side comparison.
| Feature | PWA (2026) | Flutter | Kotlin Multiplatform |
|---|---|---|---|
| Install size | 5‑10 MB (browser cache) | 30‑50 MB (runtime + engine) | 10‑20 MB (shared lib + native UI) |
| Access to OS APIs | Full via Service Workers, Web Share, Payment, Camera, Geolocation | Near‑complete via platform channels | Near‑complete via Kotlin/Native bindings |
| Update latency | Instant (no app store) | App‑store review (hours‑days) | App‑store review (hours‑days) |
| Performance | Near‑native for UI‑heavy apps, slower for heavy computation | High, GPU‑accelerated, but larger memory footprint | Native UI performance, shared logic runs at native speed |
| Developer tooling | VS Code, Chrome DevTools, standard web stack | Android Studio, Dart DevTools | IntelliJ, Android Studio, Xcode for UI |
| Ecosystem maturity | 2026: Service Workers, Push, WebAuthn fully supported on iOS/Android | Stable, but community split on web support | Growing, but UI sharing still experimental |
| Monetization | In‑app purchases via Web Payments, ads, subscriptions | App Store/Play Store billing APIs | Native store billing APIs |
| Future outlook | Web standards continue to converge; no app‑store gatekeeper | Google backing, but web target still limited | Strong backing from JetBrains, but UI fragmentation remains |
Before iOS 17, the biggest excuse for native was "you can't reach iPhone users without the App Store". Now a PWA can be added to the Home Screen with a single tap, appears in search, and can receive push notifications. The friction of app store review cycles is gone, which means:
A single codebase for web, Android, and iOS means one set of CI pipelines, one set of dependencies, one set of developers. Companies report up to 40% reduction in engineering headcount for cross‑platform products that moved from Flutter/KMP to PWAs.
Modern browsers now use WebAssembly (Wasm) + SIMD for heavy compute, and WebGPU is stable on iOS 17. Benchmarks from V8 and Chrome show PWA games within 10% of native frame rates. For most business apps (dashboards, forms, media streaming) the difference is imperceptible.
Search engines index PWAs just like any website. A user can discover a product via Google, Bing, or even Apple Spotlight without opening an app store. This organic discoverability translates to higher conversion rates for startups.
Not every scenario favors PWAs. Here are the hard cases where native still dominates:
These examples illustrate that the decision is rarely binary; many teams adopt a mixed strategy.
My prediction for the next three years is a Web‑First Native model:
This approach gives you the best of both worlds: the agility of the web and the polish of native where it truly matters.
The iOS 17 breakthrough turned a long‑standing disadvantage into a level playing field. PWAs are no longer the "good enough" fallback; they are a first‑class platform for many product categories. Native frameworks like Flutter and Kotlin Multiplatform still have a role, especially for graphics‑intensive or deeply integrated experiences, but the default assumption should now be web‑first.
"If you can ship the same experience as a PWA, you should. The only time you should not is when the web truly cannot meet the requirement."
Developers who embrace this shift will enjoy faster releases, lower costs, and broader reach. The native war is not over, but the balance has tipped – and the tide is moving toward the web.
Ready to pivot your roadmap? Start by auditing your app's API usage against the latest web standards and prototype the core flow as a PWA today.
