> Markdown version of [/videos/293-native-web-apps-are-we-there-yet?t=600](https://www.wearedevelopers.com/videos/293-native-web-apps-are-we-there-yet?t=600). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Native Web Apps: Are We There Yet?

Think web apps are stuck in the browser tab? Think again. Discover how modern PWAs use deep OS integration and hardware APIs to rival native software.

- **Speakers:** [Maxim Salnikov](https://www.wearedevelopers.com/@maxim-salnikov)
- **Event:** JavaScript Congress
- **Published:** November 25, 2021
- **Duration:** 44:40
- **URL:** https://www.wearedevelopers.com/videos/293-native-web-apps-are-we-there-yet

## Summary

The dividing line between web and native applications has increasingly blurred, driven by the continuous evolution of progressive web applications (PWAs). While the web platform has historically offered unparalleled reach, evergreen browsers, and modern JavaScript engines, it often suffered from a dependency on persistent network connection and confinement to the browser tab. By leveraging active service workers and a properly configured web app manifest, developers can now deploy web applications that deliver robust, offline-ready experiences that install and run just like native desktop or mobile software.<br><br>Achieving a truly authentic native feel relies on deeply integrating applications with the underlying operating system. This presentation details capabilities stretching from UI adaptations—such as utilizing the window controls overlay to reclaim the visual title bar—to advanced bidirectional hardware connections. Developers can invoke outbound system dialogues via the web share API and file system access API, while also accepting inbound invocations through protocol handlers, file handlers, and the share target API. Initiatives like Project Fugu continually push these boundaries, safely exposing device-level sensors, contact pickers, and background task scheduling directly to front-end JavaScript.<br><br>While PWAs already offer near feature parity with native counterparts across major environments like Windows and Android, the primary hurdle to adoption remains developer awareness rather than technical limitations. Transitioning to a unified codebase architecture significantly lowers both development and ongoing support costs. Utilizing tools like PWABuilder, engineering teams can easily package their responsive applications for distribution across the Microsoft Store, Google Play, and iOS App Store. Supported by seamless hosting on platforms like Azure Static Web Apps, these enhanced web platforms provide businesses with frictionless scalability matched perfectly to deep native integration.

**Keywords:** progressive web apps, web app manifest, service worker caching, window controls overlay, web share api, file system access api, custom protocol handlers, share target api, web push notifications, project fugu, pwabuilder packaging, offline-first architecture, azure static web apps, native hardware access, single codebase architecture

## Chapters

1. **The case for the web as a developmental platform** (00:03) — Evergreen browsers and evolving execution environments provide a resilient foundation for software engineering projects.
1. **Overcoming offline dependencies with local service caching** (07:06) — Granular background data caching frees core applications from continuous server connectivity constraints.
1. **PWA adoption models and bridging native capabilities** (10:00) — Measuring modern progressive architecture usage while narrowing gaps between isolated application delivery methods.
1. **Analyzing system interaction and native integration points** (13:11) — Categorizing functional interactions across client interfaces using flags and browser feature trails.
1. **Establishing valid PWA installation and manifest criteria** (16:19) — Constructing compliant metadata objects forces browsers to recognize websites as fully standalone applications.
1. **Configuring app installation shortcuts and launch routines** (18:48) — Routing user invocations through customized desktop items allows fine-grained initialization control.
1. **Controlling window display modes and interactive overlays** (22:39) — Reclaiming framing space with layout configurations produces immersive full-screen user interfaces.
1. **Triggering outbound API integrations for endpoint sharing** (25:33) — Connecting directly to default mobile address books and local directory trees scales functional possibilities.
1. **Capturing inbound system requests and target protocols** (27:36) — Registering default URI endpoints channels customized file extensions natively into web processing layers.
1. **Leveraging native alerts and background scheduling queues** (32:19) — Dispatching scheduled alerts combined with icon badges completes local background application lifecycles.
1. **Accessing advanced device hardware capabilities via standardization** (34:17) — Standardized proposals grant secure connections to machine sensors and local environmental metrics.
1. **Hosting scalable progressive properties via edge networks** (36:21) — Deploying integrated repositories onto globally distributed server nodes guarantees reliable application delivery.
1. **Addressing strict encrypted network requirements for architectures** (37:55) — Secure delivery constraints act as non-negotiable criteria before advanced web access is authorized.
1. **Evaluating the feasibility of universal shared codebases** (38:41) — Maintaining identical code across delivery targets radically reduces long-term team support thresholds.
1. **Navigating platform vendor constraints and iOS limitations** (39:38) — Extracting features on heavily restricted mobile devices depends on emerging standardization commits.
1. **Overcoming business awareness and strategic adoption barriers** (40:59) — Shifting commercial priorities requires advocating technical web maturity beyond simple document models.
1. **Distributing packaged artifacts across native application marketplaces** (41:55) — Wrapping compliant web properties through specialized deployment tooling bridges access into guarded commercial ecosystems.

## Related Moments

- [Bridging the gap between native and web apps](https://www.wearedevelopers.com/videos/289-pwas-in-2021) (from "PWAs in 2021")
- [Introduction to progressive web apps](https://www.wearedevelopers.com/videos/453-is-your-progressive-web-app-lazy-how-to-read-and-improve-your-pwa-performance) (from "Is your Progressive Web App Lazy? How to read and improve your PWA Performance")
- [Reviewing progressive web apps and their interface limitations](https://www.wearedevelopers.com/videos/290-project-fugu-progressive-web-apps-superpowered) (from " Project Fugu: Progressive Web Apps, Superpowered")
- [Defining progressive web apps and their core advantages](https://www.wearedevelopers.com/videos/45-progressive-web-apps-the-next-big-thing) (from "Progressive Web Apps - The next big thing")
- [Expanding web capabilities to rival native applications](https://www.wearedevelopers.com/videos/225-the-state-of-the-web) (from "The State Of The Web")
- [Navigating Apple policies and progressive web apps](https://www.wearedevelopers.com/videos/875-coffee-with-developers-david-heinemeier-hansson) (from "Coffee with Developers: David Heinemeier Hansson")

## Related Articles

- [Native Web Apps: Are We There Yet?](https://www.wearedevelopers.com/magazine/83-native-web-apps-are-we-there-yet)
- [Apple iOS vs. Web Apps affects us all - help the OWA to ensure you can release apps for everyone](https://www.wearedevelopers.com/magazine/389-apple-ios-vs-web-apps-affects-us-all-help-the-owa-to-ensure-you-can-release-apps-for-everyone)
- [Web Development Best Practices: What The Data Tells us](https://www.wearedevelopers.com/magazine/84-web-development-best-practices-what-the-data-tells-us)
- [The HTML Elements That You’re Probably Over-Engineering](https://www.wearedevelopers.com/magazine/646-the-html-elements-that-you-re-probably-over-engineering)

## Related Jobs

- [Senior Software Engineer, Client Apps Platform](https://www.wearedevelopers.com/jobs/ext/1773893-senior-software-engineer-client-apps-platform) at **GitHub**
- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**
- [Senior Software Engineer, React (Websites & Martech)](https://www.wearedevelopers.com/jobs/ext/1605272-senior-software-engineer-react-websites-martech) at **Bitpanda**
- [Software Engineer, React & Angular (Broker Web Platform](https://www.wearedevelopers.com/jobs/ext/1558399-software-engineer-react-angular-broker-web-platform) at **Bitpanda**
- [Software Engineer](https://www.wearedevelopers.com/jobs/ext/1304673-software-engineer) at **Bitpanda**
- [iOS Engineer, Swift/SwiftUI/Combine (B2C Broker)](https://www.wearedevelopers.com/jobs/ext/1611832-ios-engineer-swift-swiftui-combine-b2c-broker) at **Bitpanda**