Skip to content
AVERIQ
LanguageRUEN
Discuss a project
Mobile development

When a mobile app is too early, even if you want one very much

An icon on the home screen does not make a scenario mobile. First check how the phone differs from a good account.

AVERIQ · · 2 min read

An app in a store looks like a serious product. For some tasks, it is. For the rest, it is a second client that has to be built, reviewed, and fixed in parallel with the site. Before you order the development, it helps to answer honestly what the browser cannot do.

An app fits when the phone is the place of work

  • The action happens in the field, at a point, or on the road, not at a desk.
  • The network drops, and the data cannot wait until the evening.
  • A person opens the scenario several times a day, and a browser tab gets in the way.
  • The device itself is needed: a camera as part of the process, or a push about an event that cannot be missed.

An app is too early when the scenario has not settled

If you are still testing whether people need the service at all, an app store slows what you learn. An account in the browser can go out the same day. It is easier to change, and it does not have to be explained to a review. For a first version, a web service is usually the better fit. A mobile client is added when people repeat the scenario, and the browser is already in the way.

Two clients double the price of every change

Every new role, and every field, lives on the server, on the web, and on the phone. That is normal for a mature product, and heavy for a hypothesis. Server logic should be separated from the screen from the start. Then a future phone will not need a second database, or a second version of the truth about the order.

A short test: write down the user's actions for a week. Mark the ones that are impossible in a responsive account. If the list is empty, the app can wait, and the product is not lost.

Related services

Continue reading