Store app or responsive web app: how to decide
Published by PWTECH
The question arrives as "we need an app". What the business usually needs is for customers or staff to do something on a phone. Whether that calls for an installed app from the stores or a web application that works well on a phone screen is a separate decision, and it changes the cost by a large margin.
This note sets out how we make that decision with a client. It is not a preference for either answer; some of our own work is one and some is the other.
Which one fits?
A store app earns its cost when
- People will open it several times a week, so an icon on the home screen matters
- It needs push notifications, the camera, precise location or Bluetooth hardware
- It must keep working without a signal, in a warehouse, a basement or a lift
- Your customers already expect to find you in the stores
- You can fund an update each time iOS and Android change
A responsive web application is enough when
- Visits are occasional: a yearly renewal, a booking, a form
- Everything it does works in a browser tab today
- You would rather not pay a store commission on digital sales
- You want to release a change the same afternoon, without a review queue
- The audience is staff on laptops as often as on phones
Six questions that decide it
- How often will one person use it in a normal month?
- Which phone features does it need, and which are merely nice?
- Where will it be used, and is there always a signal there?
- Who pays for the update when the next operating-system version ships?
- Does any revenue flow through it, and is it digital or physical?
- Will the same people also use it on a desktop?
Three things that change the answer
The API comes first either way
Both answers rest on the same server-side rules. If the API is built properly, a web application can gain a store app later without a rewrite, which makes starting with the web the lower-risk order.
Install prompts on the web
A web application can offer an icon on the home screen and work offline for many uses. For a field tool used daily that may be enough, and it avoids the stores entirely.
Two stores, two review queues
A store app is two listings, two sets of screenshots and two reviews for each release. That overhead is permanent and belongs in the budget from the start.
Asked before a mobile project
Can we have both?
Yes, and that is the common end state. We plan the API so the second front end is an addition, not a second project.
Which cross-platform framework do you use?
React Native when the web front end is already React and the team writes TypeScript; Flutter when the design is highly custom. Native when the app leans hard on the device.
What does the first step cost?
A short discovery that produces the screen flow, the decision between store and web with reasons, and a cost range. That document is yours whichever route you take.
Tell us who will use it and how often
The users, the three things they must be able to do and where they will be when they do them. That is enough to give you a first answer. We reply within one business day.