Customer apps
Accounts, catalogues, ordering, notifications and updates — for businesses whose customers come back more than once.
- Accounts
- Orders
- Push
Service 02 of 05 — App development
An app people keep installed.
Android and iOS apps for customers, field staff and internal teams — scoped tightly, shipped in stages, and maintained after release.
One builder
You talk to the person writing the code, not an account manager.
No handoffs mid-project.
Scope first
Written scope and price before work starts. Changes are priced before they are built.
No surprise invoices.
Your accounts
Domain, hosting, repositories and model keys stay in your name.
Everything is handed over.
After launch
A fix window is agreed in writing, with a maintenance option if you want one.
I do not disappear at go-live.
Scope
What this covers.
An app only earns its place if people open it more than once. That is why this work starts with the repeat workflow, not the feature list, and why a mobile web page is sometimes the more honest answer.
Field & ops apps
Jobs, checklists, photos, signatures and offline capture for staff who work away from a desk.
- Offline
- Camera
- Sync
Internal tools
Replace the spreadsheet and the WhatsApp group with one place the team can actually trust.
- Roles
- Records
- Reports
Release & upkeep
Store listings, builds, crash reporting and the version updates that follow a release.
- Stores
- Builds
- Updates
How it runs
Four steps, no mystery.
The same sequence on every project. You always know what is being built, what it costs and what happens next.
01
Scope
We map the screens, the data and the one workflow the app must get right. Everything else is phase two.
02
Prototype
Clickable screens before code. You use the flow yourself and we cut what does not earn its place.
03
Build
Cross-platform or native, chosen for the job. A working build you can open at each review.
04
Release
Store submission, listing assets, crash reporting, and handover of the codebase and backend.
Deliverables
What you get, and what I need.
No vague handover. The list on the left is what leaves my hands; the list on the right is what I need from yours to make it happen.
What you get
- Android and iOS builds from one codebase where the job allows it
- A backend and database sized to your actual volume
- Store listings, screenshots and release notes prepared
- Crash and error reporting from the first release
- Source code and cloud accounts in your name
- A written fix window after release
What I need from you
- A clear description of the one workflow that matters most
- Access to any existing system or data the app must use
- Test devices, or a decision on which ones to support
- Someone available to test builds each week
- Apple and Google developer accounts, or help opening them
Straight answers
What I won't promise.
Most studios sell certainty they cannot deliver. These are the claims I will not make, and what I do instead.
If any of these matter to you, say so on the call.
- 01App Store approval.I prepare the listing and build to the guidelines. The store makes the final call, not me.
- 02Zero maintenance.OS updates and store rules change. Budget for a maintenance window or the app will age.
- 03The same app for every use case.If a mobile web page solves it, I will say so and save you the build.
- 04A fixed date before the scope is known.Dates come with the written scope, not before it.
Keep looking
The other four.
Start here
Tell me what you are building.
A short description is enough to start. I will reply within a day with whether I can help, what it would take and a straight answer on budget.