A PWA development company builds progressive web apps: websites that install to the home screen, open in their own window, load quickly on slow connections and keep working when the signal drops. At 95 Solutions we build new PWAs from scratch and upgrade existing websites and web apps into installable PWAs. You get one codebase that runs on iPhone, Android, Windows and Mac, updates the moment you deploy, and does not need an app store review for every change.
PWAs are part of our web application development work. They suit field teams, booking and ordering tools, customer portals, catalogs and content products where people come back often but a full native app would be more than the job needs. We are also honest about the limits, especially on iPhone, and we will tell you in discovery if a native or cross-platform app is the better choice.
What Is a Progressive Web App (PWA)?
A progressive web app is a website built with three extra pieces that let browsers treat it like an installed app. The word progressive means the app works as a normal website for everyone, then adds app features on devices and browsers that support them.
- A web app manifest. A small JSON file with the app name, icons, theme color, start URL and display mode. It tells the device how the app should look once installed.
- A service worker. A script that sits between the app and the network. It caches files and data so screens load instantly and keep working offline, and it receives push notifications.
- HTTPS. Service workers only run on secure origins, so a PWA must be served over HTTPS.
Everything else, from the interface to logins and payments, is ordinary web development. That is why PWAs cost less to build and maintain than separate iOS and Android apps, and why the quality of the underlying web app matters so much.
Our Progressive Web App Development Services
| Service | What you get |
|---|---|
| PWA upgrade of an existing site or app | A manifest, icons and splash screens, a service worker with a caching plan, an install flow and offline fallback pages, added to the site you already have. |
| Custom PWA development | A new app-like product designed for phones first, with logins, user accounts, payments and an admin panel where needed. |
| Offline-first data sync | Data stored on the device in IndexedDB, changes queued while offline and synced when the connection returns, with clear rules for conflicts. |
| Web push notifications | Permission prompts placed at the right moment, push delivery through the Web Push protocol, and a simple dashboard for your team to send messages. |
| App store packaging | Google Play listing through a Trusted Web Activity and Microsoft Store packaging, prepared with tools such as PWABuilder and Bubblewrap. |
| Storefront PWAs | Fast, installable shopping front ends for headless commerce setups, including Magento and Adobe Commerce stores. |
| PWA performance optimization | Caching, code splitting, image work and Core Web Vitals fixes for a PWA that has become slow or stale. |
| Maintenance and updates | Service worker updates, browser change testing and new features after launch. |
What a PWA Can and Cannot Do on iPhone, Android and Desktop
Browser support decides what a PWA can do, and it is not the same everywhere. This is the summary we walk through with every client before the scope is fixed. Browsers change, so we recheck the details for your feature list during discovery.
| Capability | Android (Chrome) | iPhone and iPad (Safari) | Desktop browsers |
|---|---|---|---|
| Install to home screen or desktop | Yes, with an install prompt the app can trigger | Yes, but the user adds it through the Share menu. There is no automatic install prompt. | Yes, from the address bar or an in-app button |
| Offline screens and caching | Yes | Yes | Yes |
| Push notifications | Yes | Yes since iOS 16.4, but only after the app is added to the home screen and the user grants permission | Yes |
| Background sync while closed | Yes, through the Background Sync API | No, sync happens when the app is opened | Yes in Chromium browsers |
| Bluetooth and NFC | Web Bluetooth, and Web NFC in Chrome | No | Web Bluetooth in Chromium browsers |
| Payments | Google Pay and cards through the Payment Request API | Apple Pay on the web and cards | Cards, Google Pay, Apple Pay in Safari on Mac |
| Store listing | Google Play through a Trusted Web Activity | App Store needs a native wrapper and must pass Apple's minimum functionality rule | Microsoft Store accepts PWAs |
If your app needs Bluetooth hardware, background location or reliable background work on iPhone, a PWA is the wrong tool and we will recommend a native or cross-platform build instead.
How Our PWA Development Company Builds and Launches an App
- Discovery (about 1 week). We list the screens, the data each one needs offline, the devices your users carry and the features that depend on browser support. You get a written scope, a caching plan and a fixed price.
- Design (1 to 2 weeks for a new PWA). Phone-first screens in Figma, plus the installed-app details people forget: icons for every platform, splash screens, the offline page and how the install invitation appears.
- Build (2 to 4 weeks for an upgrade, 6 to 12 weeks for a new PWA). Work happens in two-week cycles on a staging URL you can install on your own phone, so you test the real thing as it grows.
- Offline and sync testing. We test in airplane mode, on throttled connections and across app updates, because the hardest PWA bugs appear when a cached old version meets a new server.
- Device testing and launch. Real iPhones, Android phones and desktop browsers, an accessibility pass and a Core Web Vitals check. Then we launch, add install tracking to your analytics and, if you want, submit to Google Play and the Microsoft Store.
PWA Caching Strategies and Offline Mode, Explained
Offline mode is not a switch you turn on. Each type of content needs its own rule, and choosing the wrong one is the most common reason a PWA shows stale prices or loses form data. These are the standard strategies we pick from.
| Strategy | How it works | Best for |
|---|---|---|
| Cache first | Serve from the device cache, only go to the network if the file is missing | Fonts, icons, versioned scripts and styles |
| Network first | Try the network, fall back to the cache when offline | Account pages, order status, anything that must be current |
| Stale while revalidate | Show the cached version at once, fetch a fresh copy in the background for next time | Catalog pages, articles, menus |
| Network only | Never cache | Checkout, payments, admin actions |
For data the user creates offline, such as a delivery note or an inspection form, we store the record in IndexedDB, show it as pending and send it when the connection returns. Every record carries an ID created on the device, so a retry never creates a duplicate on the server. We also build the update flow on purpose: when you deploy a new version, the app tells the user an update is ready instead of silently mixing old and new files. This app shell approach is what makes a PWA feel instant on the second visit.
PWABuilder, Workbox and Our PWA Development Stack
| Category | Tools |
|---|---|
| Frameworks | Next.js, Nuxt, SvelteKit, Angular, React with Vite, or your existing PHP or Laravel app |
| Service worker | Workbox, the Vite PWA plugin, Angular service worker |
| Offline data | IndexedDB with Dexie.js, the Cache API |
| Push notifications | Web Push with VAPID keys, Firebase Cloud Messaging, OneSignal |
| Packaging for stores | PWABuilder, Bubblewrap for Trusted Web Activities |
| Testing | Chrome DevTools Application panel, Safari Web Inspector, Playwright, Lighthouse, real devices |
| Hosting | Cloudflare, Vercel, AWS, DigitalOcean |
PWABuilder, the open-source project from Microsoft, is handy for generating a manifest and store packages, but it does not write your caching strategy or offline logic. A PWA builder tool gets you an installable shell. The work that makes the app useful offline still has to be designed for your data.
PWA vs Native App vs Mobile Website
| Option | Choose it when | Trade-offs |
|---|---|---|
| Responsive mobile website | People visit occasionally and mainly read or buy once | No install, no offline mode, no push |
| Progressive web app | People return often, need fast access, offline screens or push, and you want one codebase | Limited device access and no install prompt on iPhone |
| Cross-platform app | You need App Store and Google Play presence and deeper device features on both platforms | Store reviews for each release, two store listings to maintain |
| Native iOS or Android app | The product depends on hardware, background work or the newest platform features | Separate codebases and the highest build and maintenance cost |
A PWA is also a sensible first step. Many products launch as a PWA, learn what users actually do, and only then invest in cross-platform app development or a native iOS app. The backend API carries over either way.
PWA SEO: Keeping a Progressive Web App Visible in Google
A progressive web app is still a website, so it can rank like one, but only if search engines receive real content. Many PWAs are built as single-page apps that send an almost empty HTML file and draw everything with JavaScript. Google can render JavaScript, but it does so later and less reliably than reading plain HTML, and other crawlers and AI tools often do not render it at all.
- Server-side rendering or pre-rendering. Public pages are rendered on the server with Next.js, Nuxt or SvelteKit, so the first response contains the content, title and links.
- Real URLs. Every screen has its own URL, with no hash-based routing, so each one can be shared, linked and indexed.
- No content behind the service worker. Search engines read what your server returns. The offline cache improves speed for returning users but must never be the only place content lives.
- Metadata on every route. Unique titles, descriptions, canonical tags and structured data per page, not one set for the whole app.
When search traffic matters, we plan the PWA with our technical SEO team from the first sprint rather than fixing indexing after launch.
Ecommerce and Magento PWA Development
Online stores were early PWA adopters because speed and repeat visits matter so much to revenue. For Magento and Adobe Commerce, the common routes are Adobe's PWA Studio or a separate storefront such as Alokai (formerly Vue Storefront) connected through the Magento APIs. For other platforms, a headless storefront built on Next.js can act as a PWA in front of Shopify, BigCommerce or WooCommerce. The right route depends on your catalog, your checkout and who will maintain the front end. Our headless commerce development team scopes these builds, and existing Magento stores can be reviewed alongside our Magento development work.
PWA Deliverables and How We Measure the Launch
- Source code in your GitHub organization, hosted in your own Cloudflare, Vercel or cloud account.
- Manifest, full icon set and splash screens for iPhone, Android and desktop.
- A documented caching plan showing which strategy each route uses and why.
- Push notification setup with keys stored in your accounts and a simple sending screen.
- Install, offline and push events tracked in GA4 so you can see real adoption.
- Store listings for Google Play and the Microsoft Store if they are in scope.
After launch we look at measures the build controls: Core Web Vitals on real devices, how many visitors install the app, how often installed users return, offline submissions that synced without error, and push opt-in rates. We do not promise traffic or sales figures, because those depend on your offer and marketing.
PWA Development Pricing
PWA work is priced as fixed-price projects. Upgrading an existing site is the smallest job, because the screens already exist and the work is the manifest, service worker, offline rules and install flow. A new PWA is priced by the number of screens, logins and payments, how much data must work offline, push notifications and any integrations. Maintenance after launch can run on a monthly plan.
PWA Upgrade
$1,500 one-time
One-time, 50% upfront
- Turn your existing website or web app into an installable PWA
- Web app manifest, icons and splash screens
- Service worker with offline caching
- Push notifications set up
- Lighthouse PWA and speed audit
- Delivered in 2 to 3 weeks
PWA Starter
From $7,500 project
Milestone billing
- New PWA with up to 10 screens (catalog, booking or content)
- Installable on iPhone, Android and desktop
- Offline mode for key screens
- Push notifications
- CMS or admin panel
- 60 days support
PWA App
From $12,000 project
Milestone billing
- App-like product with up to 25 screens
- Logins, payments and user accounts
- Offline-first data sync
- Push notifications and background sync
- API and admin panel
- One codebase for web, iPhone and Android
- 60 days support
All prices in USD. Need something different? Ask for a custom quote.
If your project sits between these plans, describe it to us and we will send a custom quote with a suggested scope.
Progressive Web App Mistakes We Fix
- Caching HTML forever. Users see last month's prices because the service worker never fetches a new page. Pages need a network-first or revalidate rule.
- No update flow. Old cached scripts talk to a new API and break. We version caches and tell users when an update is ready.
- Asking for install or push on the first visit. People decline prompts they do not understand yet. We invite them after a meaningful action, such as a second order.
- Assuming iPhone works like Android. No install prompt, push only after install, and no background sync. We design the iPhone experience separately with instructions where needed.
- Losing offline form data. Forms that fail silently when the signal drops cost real work. We save drafts on the device first.
Why Choose 95 Solutions as Your PWA Development Company
- Web performance is our daily work. We run our own content sites on a custom PHP CMS and co-build AM Jarvis, a SaaS suite for Shopify and WooCommerce stores, so caching, speed and indexing are problems we solve on our own products.
- Development and SEO in one team. Your PWA is built to be indexed and measured from the start, not patched later.
- Senior-led and honest about limits. Mustafa, our founder, holds a BS in Computer Science and leads every engagement. If a PWA cannot do what you need on iPhone, we say so before you pay for it.
- You own it all. Code, hosting, push keys and store listings sit in your accounts, invoiced in USD from our US LLC.
Who Our PWA Development Services Are For
A good fit
- Businesses with field staff who need forms and job lists that work with poor signal.
- Booking, ordering and loyalty tools used by returning customers.
- Companies with a web app that users keep asking to install.
- Startups that want to test a product on every device before funding native apps.
- Stores and publishers that want faster repeat visits and home screen access.
Probably not a fit
- Apps that need Bluetooth hardware, background location or heavy background processing on iPhone.
- Products where App Store discovery is the main acquisition channel.
- Sites with mostly one-time visitors, where a fast mobile website is enough.
Related Services Around Progressive Web Apps
A PWA usually sits on top of a larger web app. Our custom web application development team builds the backend and admin side, and when you outgrow the browser, our mobile app development team can reuse the same API for native or cross-platform apps.