Updated
How to build a mobile app for your business
In short
Start with one problem the app has to solve and the smallest version that solves it. Then pick the form: a web app that opens from a link, the fastest way to launch, or an app in the App Store and Google Play, when you need background location, reliable notifications on every phone, a store presence or daily use. The path is always the same: a plan, screens you try on your phone, short build cycles, testing with real people, then release.
1. Define the problem, not a feature list
Apps that fail usually start from a long wish list. Write one sentence saying who uses the app and what they do with it, for example "customers book a slot without calling" or "drivers log deliveries from their phone".
That sentence gives you the first version: only the screens needed for that one job. Everything else goes on the later list, for when you've seen how people actually use it.
2. Web, app stores, or both?
- Web app (PWA): opens from a link or QR code, can be added to the home screen and skips app store review. The quickest choice for bookings, orders, menus and client portals.
- App Store and Google Play app: worth it when you need background location, reliable notifications on every phone, deeper device features, or when people open it every day.
- One codebase for iOS and Android: with React Native or Flutter you build a single app for both phones instead of two separate ones.
- Many products start as a web app and go into the stores once the user base grows.
3. Screens you can try on your phone
Before any code, the screens are drawn and linked into a prototype you open on your own phone. This is where changes are cheapest: move buttons, cut steps, show it to two or three customers. An hour of testing here saves weeks later.
4. Building in short cycles
The app is built in one- or two-week cycles, and at the end of each you see something that works. Alongside the screens comes the part you don't see: user accounts, the database, the admin panel where you manage bookings, orders or content, and notifications.
5. Publishing to the App Store and Google Play
- Apple needs an Apple Developer account with a yearly fee, and every version goes through Apple's review before release.
- Google Play needs a developer account with a one-off fee. New personal accounts must test the app with at least 12 testers for 14 days before release. Organisation accounts skip this but need the company's D-U-N-S number.
- Both stores require a privacy policy, screenshots, a description and, if the app has a login, a demo account for the reviewers.
- Open the store accounts in your business's name, so the app stays yours.
How long it takes
It depends on the number of screens and what has to be connected: payments, maps, software you already use. A web app with a few screens takes weeks. An app with accounts, payments, an admin panel and release in both stores takes months. Only a week-by-week plan, made once the first version is defined, gives you a real date.
What to have ready
- The one-sentence problem and who uses the app.
- Logo, colours and main texts, or who will prepare them.
- How you'll take payments: card payments need an online payment service from your bank or another provider.
- Who runs the app after launch and how you'll answer users.
How we work
At Novaris Labs we start with a workshop on the first version, then you get a fixed price and a written plan. You see progress every week, we handle store release and review, and the code and accounts are yours. Kupon, our own web app that reads Albanian fiscal receipts from the tax office, runs live in any phone browser.