"How much will my app cost?" is the first question most founders ask me. For a Progressive Web App (PWA) there is no single price, but the cost is easy to predict once you know what drives it. This guide explains those drivers in plain English.
Why a PWA usually costs less than native apps
A native product often means two apps, one for iPhone and one for Android, plus a website. A PWA is one codebase that runs on phone, tablet and desktop. You pay for one build, one set of tests and one release process. There are also no app store fees or review delays.
The six things that drive the cost
- Number of screens and user roles. A booking app with one type of user is small. A product with customers, staff and admins is three apps in one.
- Offline support. Showing saved pages offline is simple. Letting users create and edit data offline, then syncing it safely, is the most expensive part of many PWAs.
- The backend. Most apps need an API, a database, sign-in and an admin panel. This is often half of the total work.
- Payments and integrations. Stripe, maps, email, SMS and other third-party services each add time for building and testing.
- Design. Using a ready-made design system is quick. A fully custom look takes longer.
- Testing on real devices. iPhone and Android behave differently for install, storage and notifications. Good testing prevents surprises after launch.
Typical project sizes
These are the timelines I usually see in my own projects. Your price is the time multiplied by your developer's rate.
- Small: 3 to 6 weeks. A simple installable app with a few screens, sign-in and a basic backend. Example: a booking or ordering flow.
- Medium: 2 to 3 months. Several user roles, an admin dashboard, payments and some offline use.
- Large: 4 months or more. Full offline-first work with data sync, multi-tenant accounts, subscriptions and reporting.
Running costs after launch
Plan for a small monthly budget as well as the build:
- Hosting and database
- Email, SMS or map services, if you use them
- Maintenance: security updates, bug fixes and small improvements
For a new product these costs start low and grow with your users.
Five ways to keep the cost down
- Launch with the core flow only. Build the one thing users cannot do without. Add the rest after real feedback.
- Add offline editing only where it is needed. Most apps need it on a few screens, not all of them.
- Use proven services. Do not build your own payments, email or sign-in system.
- Ask for a fixed price per milestone. You see working software before you pay for the next step.
- Hire one full stack developer for a small product. You avoid hand-offs between a front-end and a back-end person.
Questions to ask before you accept a quote
- Does the price include the backend, hosting setup and testing on real iPhones and Android phones?
- Which screens work offline, and what happens to data entered offline?
- Who owns the source code and the accounts at the end?
- What does support cost after launch?
Want an estimate for your app?
Send me a short description of your idea and I will reply with a practical plan and a rough size. See my PWA development page, read how to hire a PWA developer, or see how I built an offline-first PWA for field teams.