A mobile app for your business: when it pays off and what to settle first
Not every business needs an app. When one makes sense, what to ask before you get a quote, and why it matters where its data lives.
“We need an app” is one of the most expensive sentences in a business, if you do not know exactly what for. An app nobody opens costs as much as one used every day. Here is how to tell which one you are about to build.
The question to start from
Not “we want an app too”, but “what will people do in it several times a month?”. People install and keep the apps they use often. If a customer looks you up once a year, a good website is enough.
An app makes sense when:
- customers come back often: salon, clinic, gym or repair shop bookings;
- customers buy from you often and want to reorder quickly, with address and payment saved;
- your team works in the field: technicians, reps or drivers who need jobs, records and time tracking on the phone;
- you want to send useful notifications: booking confirmed, order shipped, results ready.
An app for customers, an app for your team
They are two different things and worth keeping apart.
The customer app has to be simple and fast: booking, ordering, account, history. It is judged by how quickly it gets the customer’s task done.
The team app has to be practical: today’s jobs, the customer record, a photo of the receipt, clocking in. It is judged by how many calls to the office it saves.
Where the data lives: the question everyone forgets
Most apps fail not because of design but because of data. The app has its own database, the ERP has another, and the two “sync”. In practice that means double bookings, wrong stock and someone fixing the differences.
The healthy option is for the app to hold no data of its own for the things that matter. It reads and writes directly into the system the business runs on, through an API:
- a booking made in the app shows up in the front desk calendar right away;
- an order draws from the same stock as the online store;
- the customer account is linked to their record, with invoices and history.
The idea behind it, in short: headless in plain words.
What to settle before the quote
- Who it is for and what they do there most often (three things at most).
- What already exists: customers, bookings, catalog, accounts. Anything that exists does not need building again.
- Offline: does the field team have signal everywhere? If not, the app has to keep data on the phone and send it later.
- Notifications: which messages and when, so they do not turn into spam.
- Whose developer account it is: the app should be published under your company’s account, not the agency’s.
Native or cross-platform?
For most businesses, a cross-platform app (React Native or Flutter) is the right call: one codebase for iOS and Android, so lower cost and faster updates. Native makes sense when the app relies heavily on phone features.
Have an app idea?
Tell us who it is for. We will show you what already exists in the ERP and what needs building.
See also mobile apps on RIVIL and, if you need something bigger, platforms.
