The Browser Becomes the Platform
A decade ago, web apps were second-class citizens. "Real" software required installation. Native applications were faster, more powerful, and more reliable. The web was for documents, not applications.
That era is ending. Modern web apps run offline, send push notifications, access hardware, and rival native performance. The line between "website" and "application" has blurred beyond recognition.
The Progressive Web App Revolution
Progressive Web Apps (PWAs) represent the web's answer to native limitations:
- Twitter Lite: 65% increase in pages per session, 75% more tweets sent
- Starbucks: PWA is 99.84% smaller than iOS app
- Pinterest: 60% increase in core engagements
New Browser Capabilities
Modern browsers offer APIs that were unimaginable a decade ago:
| Category | APIs Available |
|---|---|
| 🎨 Graphics | WebGL, WebGL2, WebGPU (near-native 3D) |
| 🔌 Hardware | Web Bluetooth, Web USB, WebXR (VR/AR) |
| ⚡ Performance | WebAssembly, Web Workers, SharedArrayBuffer |
| 💾 Storage | IndexedDB, Cache API, File System Access |
| 🌐 Network | WebRTC, WebSockets, Service Workers |
The "Install" Model Is Broken
Traditional software distribution has serious problems:
Web apps solve all of these: instant access via URL, minimal storage, always-current code, and universal platform support.
What the Web Still Can't Do (Yet)
Despite progress, some native advantages remain:
Background processes, system tray, file type associations, and deep OS hooks remain native territory. PWAs are getting better but can't fully replace system-level integration.
For AAA games and professional applications (video editing, 3D rendering), native still offers better performance. WebGPU is closing this gap rapidly.
Centralized distribution with built-in billing infrastructure remains a native advantage. Though the 30% cut makes this a double-edged sword.
The Hybrid Approach
Increasingly, the answer isn't "web or native" but "web and native":
Package web apps as desktop applications. VS Code, Slack, Discord are all Electron apps.
Wrap web apps for mobile app stores with access to native features.
System webviews for smaller bundle sizes than Electron. Rising rapidly in popularity.
What This Means
| For Developers | For Users |
|---|---|
| One codebase for all devices | Less storage consumed |
| URL distribution beats app stores | Fewer accounts to manage |
| Ship fixes instantly | Flexibility to switch devices |
| Web skills apply everywhere | Reduced vendor lock-in |
- PWAs are real: Twitter, Starbucks, Pinterest prove enterprise viability
- Browser APIs exploding: WebGPU, WebXR, File System Access close native gaps
- Install model is broken: Friction, storage, updates, platform lock-in
- Hybrid wins: Electron, Tauri, Capacitor bridge web and native
- Future is mixed: Not purely web or native, but an expanding web portion
The Bottom Line
The future isn't purely web or purely native—it's a spectrum. But the web's portion of that spectrum is expanding rapidly. For many application categories, the question isn't whether web apps are good enough, but whether native apps are worth the additional complexity.
The browser has quietly become the world's most powerful application platform. And it's only getting started.
- web.dev PWA Documentation
- W3C Web Platform Capabilities
- State of JS Survey - Framework Usage