An App in the Store or a Web App: What a Business Actually Needs
We built four business apps. Not one client asked for them to be in a store. One of them is used by a whole team every morning and it opens from the phone browser like any website. That is not giving something up. In most cases where a business asks for an app, what it is asking for is a screen that works well on a phone.
The assumption a business owner walks in with
Almost every conversation about an app starts at the same point. The owner assumes an app is something that sits in a store, that you download it, that it has an icon on the screen. That is their definition of the word.
Then it turns out what they need is for the worker in the field to mark a task done. Or for the customer to book a slot. Or for a manager to see what happened today without driving back to the office. **None of those needs a store.**
That assumption costs money. An app built twice, once for iPhone and once for Android, costs more than double the same system running in a browser. And that is before we talk about what happens after launch.
There is a quieter trap in it too. The road from idea to store is long. While it runs the business carries on without the system exactly as before. We have seen enough systems stall in the planning stage because someone wanted everything perfect before launch. A system that went up partially and serves the team tomorrow morning is worth more than a complete one arriving in six months.
What a web app actually is
A web app (PWA) is a system that opens in the phone browser and behaves like an app. You can add it to the home screen with its own icon, it opens full screen with no address bar, and it remembers who you are between visits.
In practice the user cannot tell the difference. They tap an icon and a screen opens. The only thing they will notice is that the first install came from tapping a link rather than from a store.
What is different is what happens behind the scenes, and the advantage there is large. **A fix goes live immediately.** No waiting for a store review, no begging users to update, and no situation where half of them are running a version four months old.
When a store is the right answer
There are cases where the store is not a whim. They are usually one of two.
The first is a real need for hardware or a capability the browser does not give. Heavy camera use, continuous work with no network, or notifications that must arrive on time even when the app is closed. If your business leans on one of those, that is a good reason.
The second is when the store itself is the distribution channel. An app aimed at a wide audience that will search for it in a store, like a game or a mass consumer service, finds its customers there. A business whose users are known by name and get a link on WhatsApp does not need that.
Most of the businesses we meet in Eilat are in the second category. The team is known. Customers arrive from search or from a recommendation. There is no anonymous audience looking for them in a store.
What nobody tells you about the store
The part that disappears from the conversation is not the build but what comes after it. Three things that keep costing time and money every year.
- A paid developer account, annually, in each store separately. That is the price of staying live
- A review for every update. Even a one line fix goes through checking, and meanwhile the bug is live
- Users who do not update. Part of the team will keep working on an old version for months and you will support both at once
Why it works in the field
One of the systems we run is used by a whole team every morning. Ten people and more open it at the start of the shift from their own phones. It is not in a store and none of them has asked why.
The reason is simple. **A worker does not download an app. They tap a link their manager sent.** The first time, they add it to the home screen and from then on it looks to them exactly like any other app. Had we sent them to a store, part of the team would have got stuck at the download step and the rest would have arrived there a week later.
Another system runs at several organisations at once, each with its own team and its own data kept separate. No request for a store came up there either. We expanded on how systems like these are built on the apps page.
What it costs. The honest answer
That is the first question asked and it has no single answer. **Anyone who quotes a price or a timeline before knowing what the system does is guessing.** The gap between one screen showing a list and a system with permissions and reports and payments is a gap of several times over, not of percentages.
What can be said with certainty is the relative difference. The very same system, built twice for two stores, will cost more than double the same system in a browser. And it will keep costing every year in maintaining two versions instead of one.
The right way to ask is not what an app costs. It is what the system has to do on day one and what can wait. We explained the same logic in our guide to website cost and it holds here.
And if in two years we do want a store
This is the question that actually stops people. They worry that choosing web today closes a door tomorrow.
It does not. A system is split into two layers. There is the logic that holds the data and the permissions and the calculations. And there is the screen the user sees. **Moving to a store touches only the second layer.** Everything built underneath keeps working as it is.
Which means starting with web is not a dead end but an invitation. You launch fast, you find out what the team actually uses and what sits abandoned. And if one day it turns out you need a store, you walk in with a mature system and a real list of requirements instead of guesses.
The opposite is what carries risk. Building straight for two stores before you know what the system needs to do is paying twice for a guess.
And what not to build at all
This is the part we say even when it closes work for us. **If your idea already exists in dozens of versions on the market, do not build it.** Not because you cannot, but because your user needs a reason to switch and does not have one.
That is especially true of general consumer apps. A task list. A calorie counter. A workout log. The market there is saturated. The competitors are well funded. The only thing that would set you apart is a marketing budget you do not have.
What does work is the opposite. A system that solves a narrow and very specific problem in one industry, where someone lives it and knows exactly where it hurts. The four systems we built are exactly that and not one of them is aimed at everybody.
How to check for yourself before talking to anyone
Before you ask for a quote, sit with these three questions. They save most of the conversation.
- Who is the user and how do they reach you. If they get a link on WhatsApp you do not need a store
- Does the system have to work with no network or use the phone hardware. If so, that is a real reason for a store
- What happens when something breaks on a Friday. If the answer you want is a fix within the hour, a store adds days of waiting for review
This is exactly what we do at App and system development. If you want us to go over it together for your business, write to us.
Frequently asked questions
A web app opens in the phone browser and can be added to the home screen with its own icon. The user usually cannot tell the difference. What is different is that a fix goes live immediately with no store review and with no need for users to update.
When there is a real need for hardware or a capability the browser does not provide, like continuous work with no network or notifications that must arrive even when the app is closed. Or when the store is the distribution channel itself, for a consumer app people will search for by name.
There is no single number and the gap between a simple system and a complex one is several times over, not percentages. Anyone quoting a price before knowing what the system does is guessing. What is known is that building twice for two stores costs more than double the same system in a browser.
No. Once the system is added to the home screen it looks and behaves like any other app, with an icon and full screen. The only difference the user experiences is that the install came from tapping a link rather than from a store.
Check how many versions of it already exist. If the market is saturated, the user needs a reason to switch and does not have one, and the only thing that would set you apart is a large marketing budget. A system solving a narrow problem in one industry is a much better bet.
Want us to look at this for your business?
Just write to us on WhatsApp. The first conversation comes with no commitment. 050-294-0127
Write to us on WhatsApp