A PWA (Progressive Web App) is a website that installs on a phone like an app: its own icon on the home screen, full-screen mode, notifications, working on a weak connection. For the first version of a product it is often the fastest way to test the idea with real users.
What a PWA can do
- Install to the home screen on Android and iPhone, without an app store.
- Open full screen, without the browser address bar.
- Send push notifications (on iPhone since iOS 16.4, after adding to the home screen).
- Cache data and the interface, and partly work offline.
- Use the camera, geolocation and files through browser APIs.
- Update instantly: ship a new version and every user already has it.
What a PWA cannot do, or does worse
- It does not appear in App Store and Google Play search – users have to be brought in by a link or a QR code.
- Limited access to system features: background tasks, Bluetooth on iPhone, deep OS integration.
- Store in-app purchases are not available – payments are taken on the website.
Comparison
| Criterion | PWA | Store app |
|---|---|---|
| Time to first version | shorter: one codebase, no review | longer: iOS and Android builds, publishing |
| Publishing | not needed, works by link | App Store, Google Play, RuStore review |
| Updates | instant | via a store update |
| Store search | no | yes |
| Access to phone features | the main ones | full |
When to start with a PWA
- A product for employees or customers you bring in yourself: shifts, requests, a customer account.
- You need to test the idea quickly and collect feedback.
- You need to update features often without store review.
An example is Vahtify, an app for parcel pickup points: chats, shift check-ins, schedules. It first went live as a PWA at real locations, and the store versions are being built after testing with users.
When to go to the stores right away
- Users will look for you in the App Store and Google Play.
- You need features unavailable from the browser: background geolocation, Bluetooth devices, complex camera work.
- The business model is in-app subscriptions.
The path we recommend
Tell us about your product in a request – we will suggest the scope of the first version and a path to the stores.