In Progressive Web App is web and app in one, and a bit more: a PWA is structured like a website (with HTML, CSS and JavaScript), but it feels like an app - including access to the smartphone camera or peripheral devices.
The prehistory
Apps have been around for a long time. In the past, they were simply called programs. They were installed on your computer and then started. Websites were a different matter - interactivity was limited to simple actions.
A lot has happened since then: On the one hand, the web is always available today; on the other hand, web technologies have penetrated many areas that were previously reserved for native apps - Twitter in the browser and the Twitter app on the smartphone offer similar functions and user experience.
Web technologies can do that too!
The differences between apps that run natively and those that run in the browser have become increasingly blurred. Very little is missing to turn a web app into a native app. This is where the part that "progressive" stands for comes into play.
As a supplement to the basic functionality of a web app, a PWA provides an "expansion stage". The PWA can be installed on the device from the browser - without the detour via an app store - and then behaves like an app.
Short: PWA stands for a massive expansion of the possibilities of web technologies. Google and Microsoft in particular are endeavoring to make interfaces that were reserved for native apps also available for web apps. This includes, among other things:
Use of built-in hardware such as camera and sensors
Yes, thanks to Service Workers, PWAs can provide content and functions offline - similar to native apps.
Do push notifications also work on iOS?
Push notifications for PWAs have been supported since iOS 16.4, but with limitations compared to Android.
Is it possible to bring a PWA into the App Store?
Yes, PWAs can be published via "Trusted Web Activities" or wrappers in app stores, but are not absolutely necessary.
What does it cost to develop a PWA?
The costs are usually significantly lower than those of a native app, as only one codebase is maintained. Of course, there are also native solutions such as Flutter. As with all digital projects, the actual prices depend on the scope of the project.
When is a native app better than a PWA?
If deep hardware access or special features (e.g. ARKit, Health APIs, Bluetooth Low Energy) are required, a native app is the better choice.
Your advantages
Avoid dependencies
The solution is based on open standards - so you minimize the risk of burdening yourself with legacy issues.
Runs everywhere
PWAs run on all platforms: Android, iOS, Windows, macOS, Linux - with a single code base.
Deploy to update
Updates are deployed on your site - your users don't have to do anything. A deploy button replaces App Store Policies.
