Progressive Web App — app-like experience without the App Store.
PWAs are websites that behave like apps: installable on the home screen, work offline (when configured), receive push notifications, and load fast. The right choice when app-store-approved native isn't required.
Need an app-like experience on mobile without the App Store requirement and native development overhead
PWAs fill a specific gap:
When PWA is the right choice:
- The application is web-first (the web version is the primary experience)
- The audience will install from the browser (tech-savvy users)
- Push notifications are needed but native isn't worth the cost
- Offline capability matters (field workers with intermittent connectivity)
When native is better:
- The App Store is a discovery channel (consumer apps)
- The app requires native features unavailable to web (ARKit, certain Bluetooth)
- The audience expects a native app (iOS/Android installed app)
PWA requirements:
- HTTPS (required by all PWA features)
- Web App Manifest (
manifest.json) — defines the app name, icons, and display mode - Service Worker — handles caching for offline, push notification subscription
- Icons at required sizes — 192px and 512px minimum
iOS PWA limitations: iOS Safari has limited PWA support. Push notifications: available on iOS 16.4+ with specific manifest configuration. Background sync: not supported on iOS. Installability: "Add to Home Screen" must be done manually — no install prompt.
Next.js + next-pwa:
next-pwa package adds service worker and manifest generation to Next.js. Configuration is minimal for basic offline support.
Progressive Web App with service worker, offline capability, push notifications, and home screen installation
Web App Manifest
with icons and display configuration
Service Worker
with appropriate caching strategy
Offline support
for core application screens
Push notification
subscription and delivery
Install prompt
for Android (iOS requires manual)
One honest number to start.
Fixed-scope, fixed-price. The number below is the starting point — final scope is built from your brief.
Progressive Web App with service worker, offline capability, push notifications, and home screen installation
Three steps, every time.
The same repeatable engagement on every project. No surprises, no mystery, no billable ambiguity.
Brief & discovery.
We send you questions, then get on a call. Output: a written scope with every step, feature, and integration listed.
Build & ship.
Fixed schedule, weekly reviews. No scope creep unless you change the scope — and if you do, we reprice it transparently.
Warranty & retainer.
30-day warranty on every launch. Most clients stay on a monthly retainer for ongoing features and maintenance.
Why Fixed-Price Matters Here
PWA scope is the caching strategy and the offline feature set. Fixed-price.
Questions, answered.
No. PWAs are installed from the browser, not from the App Store. This is the main limitation compared to native — no App Store discovery. Some services allow publishing PWAs to the Play Store (Bubblewrap), but this is uncommon.
Tell Ryel about your project.
Describe what you’re building and what outcome you need. You’ll have a written, fixed-price scope within the week.