Android and iOS apps for work that happens in someone's hand
A courier photographing proof of delivery at the door, a field officer logging a job and tagging its location, or a customer told their order is ready — this work is easiest through an app on the phone. We build it, from the first screen to a version ready to submit to the app stores.
Who it suits
Not every need calls for an installed app. It usually does when one of these is true.
The work happens away from a desk
Your team moves around all day and records things standing up, often one-handed, with a patchy signal.
You need the camera, location, or a scanner
Photos, a location pin, or a barcode must be captured on the phone itself, not uploaded from the gallery later.
Users need alerts without opening anything
Customers or staff must know when an order arrives, a schedule changes, or a task is waiting.
People open it again and again
Someone who opens it all day is better served by a home screen icon that reopens where they left off.
What we can build
Phone features are used only where they make the work easier.
Android and iOS apps
One app for both kinds of phone, feeling natural on each.
Location-based features
Recording where a task was done and listing the nearest next stops, with permission requested clearly.
Camera and scanning
Photographing finished work, receipts, or goods inside the app, and scanning QR codes or barcodes.
Notifications
Order updates, schedule reminders, or new tasks on the phone screen, with settings so users aren't flooded.
A companion to the web version
Field teams or customers use the phone app while admins use a web version on a laptop — both reading the same data.
Preparing the store listing
We prepare the name, description, screenshots, and privacy policy, then submit from a developer account you own.
How the process works
Button sizes and permission prompts only feel right or wrong once the app is in your hand, so we put it there early.
Choose the screens that must be there
We list the screens and decide which must exist at first release and which can wait.
A prototype on your phone
You try the screen designs on your own phone; awkward flows are easier to spot in the hand than on a laptop.
Testing on real devices
A test version goes on your team's phones, including older small-screen ones, and is used for real work before submission.
Submitting to the app stores
We submit the app to Google Play and the App Store. The stores check every app themselves; how long that takes and whether it's accepted are outside our control.
What we need from you
Some of these must come from you, because they decide who owns the app.
Developer accounts in your business's name
Google Play and Apple accounts should be registered to your business so the app stays yours. Each store sets its own requirements; we guide you.
The phones your team really uses
The makes and condition of phones in daily use, including the oldest, so testing isn't only on new models.
How the app uses data
What data the app collects, such as location or photos, and why. The stores ask for this, and users have a right to know.
A tester from your team
Someone who will use the app daily, try test versions, and tell us which parts are confusing.
Questions about this service
When will the app appear on Google Play and the App Store?
We estimate the build time once the screen list is agreed. How long the store check takes is not ours to set, and a store may ask for changes before publishing; we work through those with you.
Do Android and iOS need separate apps?
Not necessarily. Usually one app can be built for both. If a feature only works on one kind of phone, we tell you at the start.
What happens when phone systems are updated?
Google and Apple periodically update their systems and store rules, so the app occasionally needs adjusting to stay installable. That upkeep can be agreed once the app is published.
Tell us who will be holding the phone
Field staff, couriers, or customers — tell us over WhatsApp what they do on their phones. We'll help judge whether an installed app is needed, or a web version is enough.