What a business app actually needs to do

A business app earns its place on someone's phone by doing one job clearly. The ones that get deleted within a week almost always tried to be a whole platform on day one; the ones that stay solve a single, specific problem and solve it fast.

The first screen decides more than people expect. An app that asks for an account, a permission and a tutorial before showing anything useful loses most people right there. The better order is to prove the value first, whatever that value is for this app, a booking, a scan, a tracked number, and ask for the account only once someone has a reason to want their progress saved.

Offline matters more here than the pitch decks assume. Coverage on the coast and in the mountains is not constant, and an app that goes blank the moment a signal drops teaches someone not to open it again. What has to work without a connection is a decision made early, because retrofitting it later usually means rebuilding how the app stores data in the first place.

Roles are the part that quietly doubles the cost. An app where every user sees the same thing is a fraction of the work of one where a customer, a staff member and an owner each need different screens and different permissions, because every role multiplies what has to be built and tested. A first version built here runs from 4,000 euros, and the honest first question is always how many of those roles the first release actually needs.