Android apps from a first version that proves the idea to the release handling logins, payments and notifications — with the yearly platform updates that keep it published.
An app is not a one-time cost, and the build quote is the part everyone compares. Google raises the API level apps must target every year; miss it and your listing stops accepting updates, then stops being offered to new devices. That is not optional maintenance, it is the price of staying published.
So we quote both halves. What it costs to build, and what it costs to keep alive — because a cheap build that gets pulled from the store in eighteen months was not cheap.
Native Android development, Play Store listing, staged rollout, and the store assets and policy declarations Google now requires.
Login, session handling and password recovery; payment gateway integration with the failure states and reconciliation that go with it.
The server side the app talks to, or integration with the one you already have, including push notifications and OTP delivery.
Testing across screen sizes and manufacturer skins, because something that works everywhere in the emulator will break on one specific phone.
Target API level raised on Google's schedule, dependencies updated, and the app kept compliant with policy changes.
What a user must be able to do, and what happens when each of those fails. Screens come out of that, not the other way round.
Enough to put in real hands. Accounts, payments and anything real-time are the three things that move cost most, so we are deliberate about when each arrives.
A physical device set, not just the emulator, before anything reaches the store.
Staged rollout, crash reporting from day one, and a fix path for whatever the first thousand users find.
We would rather say so now than three meetings in.
Three things move the number more than screen count: accounts, payments, and anything real-time. Budget yearly maintenance separately — Google raises the required API level annually, and missing it takes your listing down.
Our Android work is native and it is what we do best. For iOS we will tell you honestly whether a cross-platform build fits what you need or whether you are better served by a specialist — rather than quoting for it and learning on your budget.
Three things more than screen count: user accounts, payments, and anything that has to happen in real time. An app with none of those is a straightforward project. An app with all three is a different category of work.
You. We will publish under your developer account, or set one up in your name. An app on our account is a hostage, and we do not work that way.
Describe the problem rather than the solution. We will tell you what it takes — including when the answer is smaller than you expected, or when android app development is not what you need at all.
The thinking behind the work, at more length.
The build quote is the part everyone compares. The running costs are the part that decides whether the app is still alive in two years.
Read moreWhat is happening in this corner of the industry right now.
Anthropic says an unreleased model raised the lower bound on the Riemann hypothesis after running for about a day and a half across 60 coordinated sub-agents and 650 candidate approaches. Two staff mathematicians confirmed the result and it was formalised in Lean.
Read moreCode in the iOS 27 beta describes Apple Reference Image, a system that would embed provenance data into photos at capture so they can later be verified as camera-made rather than AI-generated. It would ship switched off and verify through Private Cloud Compute.
Read moreThe Galaxy S27 Pro is set to carry a 12MP 3x telephoto while the Ultra drops its 3x entirely in favour of a 50MP 5x periscope, leaving the two hard to compare directly. A more capable ALoP prototype for the Pro appears to have been shelved to protect the Ultra's position.
Read moreWebsites and web applications built front-end to back-end — designed around what a visitor needs to do, and built so the next developer can pick them up.
What this involvesInternal tools, dashboards and integrations built around how your business actually runs — starting with the smallest version that removes the most pain.
What this involvesStores built on Shopify, WooCommerce or from scratch — chosen on what your catalogue and margins justify, not on what is easiest to build.
What this involves
