An Android app for the job you need to do
I help scope and develop Android apps for specific customer and employee tasks. We begin with users, devices and the data the app needs. The first release has an agreed scope so functionality, integrations and distribution can be verified before launch.
- I usually reply the same day
- Written estimate before work starts
star reviews
Read every reviewAndroid app development
Start with users and their devices
An internal app on company phones has different requirements from a public customer app. We describe the important tasks, screens and failure situations, including login, larger text, slow connections and interrupted journeys.
We choose technology around requirements and your existing systems. If both Android and iOS are required, we assess what can be shared and where platform work is necessary. The proposal makes those dependencies explicit.
Give data and integrations a clear owner
We agree which system owns customers, orders or cases and what permissions the app needs. Offline work requires explicit storage, synchronisation and conflict rules. Retrying a request must not accidentally create another order or record.
Access, errors and logging are scoped to the task. Representative test cases show whether the journey works. Integration failures need a visible owner and an agreed recovery procedure.
What development can include
- A brief with users, first-release scope and exclusions.
- A prototype of core screens and error states.
- Development and agreed system integrations.
- Testing on relevant Android devices and journeys.
- Preparation for the agreed distribution method.
- Code, account and documentation handover.
Agree release and maintenance responsibilities
For Google Play, we agree account ownership, release material and required declarations. Platform review is not a guaranteed approval date. Internal distribution is scoped separately.
After handover, someone needs to own errors and platform changes. We can agree ongoing work or document it for your team. An existing app or a description of its core task is enough to begin scoping.
How it works
Four steps. You know what happens when, and you can stop after any of them.
- 01 / 04
We scope the first version
A 20-30 minute call about who the app is for and what it has to do on day one. I ask about data, login and existing systems, and tell you honestly if an app is not the answer to your problem.
- 02 / 04
Screen flow before code
I sketch the screens and the path between them, so we agree on the first version before any code is written. If a design already exists in Figma, I build from that.
- 03 / 04
Development with regular testing
The app is built in scoped pieces and tested on relevant devices. iOS can use TestFlight; Android has an agreed test-distribution process. Errors and changes are handled throughout.
- 04 / 04
Release and upkeep
I prepare the agreed distribution and required materials. Platform review has its own process. Post-launch updates, errors and maintenance have explicit ownership.
Brands I've worked with
Frequently asked questions
- Can Android and iOS be one project?
- Yes. We can scope both together. Shared code and features depend on requirements and integrations. Platform-specific testing and distribution still need explicit plans.
- What does an Android app cost?
- Cost depends on journeys, data, integrations, offline requirements and maintenance. We first define a release and its dependencies, then prepare a specific estimate.