Android app from scratch
Idea or spec in, signed release on Google Play out.
- Scoping workshop and feature list
- Kotlin and Jetpack Compose build
- QA on real devices, not just emulators
- Source code and signing keys handed over
We design, build and publish Android apps on Google Play — and keep them shipping long after launch day.
Where the releases actually come from.
Four ways projects usually start. Most people arrive needing two of them.
Idea or spec in, signed release on Google Play out.
For a finished app that is stuck at the publishing step.
One scoped feature added to an app you already own.
The part that decides whether an app is still installable in two years.
Scope, timeline and cost are quoted per project after the first call — nothing is fixed until we have seen the backlog or the existing codebase.
Jetpack Compose UI, coroutines, Room or your existing storage layer. The app starts fast, handles rotation and back gestures properly, and behaves like an Android app rather than a page in a shell.
Sign-up, sign-in, password reset, session expiry and the in-app account deletion route Google now expects — built and tested as one flow, including the unhappy paths.
App signing, release tracks, staged rollouts, the data safety form and the content declarations. If a submission is rejected, we read the policy citation and answer it — we do not forward the email to you.
Existing REST or GraphQL APIs, your auth provider, your analytics. Replacing a working server is a separate decision and we will say so instead of quoting it in.
Release monitoring on the versions in the wild, reproduction on the device model that is actually failing, and a fix in the next release rather than a dashboard screenshot.
Repository, keystore, Play Console ownership, build instructions and a README someone else can follow. Nothing we build needs us to stay for it to keep running.
We had an app that worked on two phones in the office and failed everywhere else. They rebuilt the data layer, took over the Play Console release and the crash rate stopped being a weekly meeting.
Our submission was rejected twice over the data safety form before we called them. They answered the policy points, resubmitted and walked us through what each declaration actually covers.
Clear about what was in scope and what was not. The feature sprint landed with a changelog we could send to users without rewriting it.
Yes, and it is a large part of the work. We start by reading the repository and building it ourselves — if it will not build from a clean checkout, that is the first thing we fix, and we tell you what we found before any feature work is quoted.
You do. The repository, the signing keystore and the developer account stay in your name, and we work inside them. At handover you get build instructions detailed enough for another team to continue.
We read the exact policy clause cited, change what it asks for and resubmit, and explain in plain terms what triggered it. Policy rejections are part of publishing on Android, not a surprise.
Our build work is Android and Google Play. If you need both platforms we will say so at the first call rather than stretch the scope to cover something we do not ship.
Tell us your deadline in the form. We answer honestly about whether it fits the current schedule instead of booking you in and renegotiating later.
A few lines about the app is enough to start — a spec, a repository or a rough idea all work.
Thanks — someone from the team will get in touch shortly with questions about scope.
Send the idea half-formed. Scoping it is the conversation.
This page uses cookies for analytics and advertising measurement, but only after you give your consent. Learn more