Mobile apps
One codebase, both stores, and a web version of the same thing when that is cheaper.
What it is
A mobile app is worth it when people use the thing standing up: a delivery driver, a waiter, a technician on a roof.
If your customers would rather not install anything, I will say so and build a web app that works on a phone instead. That conversation happens in the first call, not after you have paid for the wrong thing.
- How long it takes
- Six to ten weeks, plus one to two weeks of store review
What is included
- React Native build for iOS and Android
- Push notifications and offline-tolerant sync
- Store submission, including the review paperwork
- A web build from the same code where it makes sense
What is not
- Apple and Google developer account fees, which are yours
- Hardware-specific work such as Bluetooth peripherals, quoted separately
How it works
An app, or a web app
On the first call we decide whether it needs to be in the stores at all. If a web app on a phone does the job, I will say so.
A written quote
A fixed price, a delivery date and what it covers, in writing. Half when you accept it, half on delivery.
Tried on your own phone
A test build you can install as it takes shape, so you use it before your customers do.
Into the stores
I handle the submission and the review paperwork; review usually takes one to two weeks. Then thirty days of fixes, free.
Who it suits
- People who use it on their feet: a delivery driver, a waiter, a technician on a call-out
- A service that needs notifications, or has to keep working on a weak signal
- A business whose customers expect to find it on the App Store or Google Play
Ask about Mobile apps
Tell me what you need. I reply within one working day, and the price and the date come out of that conversation.
Or write to me here
This goes straight to me, with the service already attached.