Android app development company UK: native Kotlin apps
As an Android app development company, we build native apps in Kotlin and hold every release to written gates on real phones. We publish under a Google Play account that you own. An Android-only MVP takes 8 to 14 weeks, and the estimator below prices your own feature list in a minute.
An Android-only MVP in 8 to 14 weeks, at one fixed price agreed after discovery
Builds 0.1, 0.2 and 0.3 on your own phone by week 8
Code, designs and Play Console in your name from day one
109
9:41
TRun 148 of 12 stops9 of 12 stopsETA4 min3 min2 min1 minArrived
9
22 Mill Lane3 parcels, side door
On the wayDelivered
7 Station RoadDelivered 10:02
103 Harbour StreetDue by 10:50
Proof of delivery10:21
Signed by M. AlderPhoto
RunMapScanMessages
Security and compliance
Cyber EssentialsCertified
Cyber Essentials PlusIndependently tested
ISO/IEC 27001:2022Information security
ISO 9001:2015Quality management
ISO/IEC 42001:2023AI management
SOC 2 Type IIAudited controls
UK GDPR andData Protection Act 2018
ICORegistered
NHS DSPTData security toolkit
WCAG 2.2 AAAccessibility
PCI DSSCard data security
How much does it cost to build an Android app?
Our four Android app development options, with the time each one takes. Price your own Android app development project with the calculator on this page, and see every price on our app development cost page. The first call is free and takes 30 minutes, and a written note on scope, timeline and price follows within two working days.
Android MVP
8 to 14 weeks
Full Android app development
4 to 8 months
Discovery
2 weeks, taken off the build price
Support after launch
Monthly, after the 3-month warranty
Android app development examples
We have been building apps since 2019. A few examples from the many Android apps we have built, what each one achieved, and a link to its full case study.
EV charging
Tiger Charge: EV charging app
What we built
We built Tiger Charge for a charging network. Drivers find stations on one map, see live charger availability and connector types, scan a charger to start and stop charging, and pay from a prepaid balance. It is a Kotlin Android app with a Node.js backend, OCPP links to the chargers and Google Maps Platform.
Over 40% of charging sessions start in the app with no call to support, and manual billing work fell by 70%
We built MyUTHealth, a patient portal app for a health provider on Epic MyChart. Patients request appointments, view test results, refill prescriptions, message their care team securely and connect Google Fit for steps, blood pressure and glucose. It runs on Android with HL7 FHIR APIs.
Downloaded 50,000+ times from Google Play and rated 4.4 stars across 750+ reviews
We built Digilite for a home automation company. Owners control and schedule appliances from anywhere, run IR devices such as TVs and air conditioners, build routines and scenes and view live energy use. They share access with family members and use Google Assistant and Amazon Alexa. It runs on Kotlin, Node.js, MQTT and WebSockets, with Zigbee, Wi-Fi and IR on AWS.
Each week, over 35% of active homes run routines or workflows, and homes use 25% less electricity once set up
“Our patients needed the portal in their pocket: requesting visits, reading test results, reordering medicines and messaging their care team. AppAgentix built the Android app on our Epic MyChart system, careful where it matters: secure sign-in, no clinical detail on the lock screen, and patients choose what fitness data they share. The app has passed 50,000 downloads with 4.4 stars from over 750 reviews, and every release was tested before it reached our patients.”
“Drivers want three things: find a working charger, start charging without fuss and pay without surprises. AppAgentix built the Android app, the prepaid wallet and the link to our chargers. Live charger status is accurate, starting a session is a scan and a tap, and the wallet settles the right amount even if the connection drops. The app has passed 10,000 downloads with a 4.1 star rating, and our manual billing work has dropped sharply.”
“A smart home app only works if the whole family trusts it. AppAgentix built our Android app so every appliance and routine sits in one place, with each family member given the right access. Commands reach the device in a moment, the app shows honestly when something is offline, and voice control works through Google Assistant and Alexa. The listing holds a 4.9 star rating. Every release was tested on real devices in real homes.”
Our rules, each with the number that sets it off and what it does to the work. The rule we used is written into your scope. In the UK, Android 16 runs on 46.61% of Android phones and Android 12 on 5.52% (StatCounter, October 2026).
Which build and which phones fit your app?
Ifover a quarter of your estimate sits in Android-specific tiles: home-screen widget, barcode scan
ChooseNative Kotlin
Outside Kotlin, each of those tiles costs about 2 to 4 more days of work.
IfiPhone must go live within 3 months of Android
ChooseFlutter
Both phones stay inside one MVP price. A second native app would add about 70% of the first.
Iftwo or more React developers on your staff will own the code after handover
ChooseReact Native
Small changes are then made in-house, not bought as Kotlin days from us.
Ifan Android version holds under 2% of your active installs
ChooseDrop that version
Each version kept costs about one test day on every full release.
Ifa version holds over 5% of installs
ChooseKeep it and test on it
A handset on that version joins the test shelf, and its extra test day a release is worth paying.
Ifa version holds between 2% and 5%
ChooseWeigh one test day a release against those users
Your scope sets the two figures side by side, from your Play Console report or, before launch, your website analytics.
Android app development services
Each service lists the named documents and builds you hold at its end.
01
Discovery
2 weeks. Scope document, clickable prototype, device list, data map and a fixed quote. Comes off the build price if you continue.
02
Android MVP
8 to 14 weeks. A signed sprint backlog, three installed test builds, the device report, data safety answers and launch under your account.
03
Full Android app development
4 to 8 months. The MVP set, plus tablet layouts, payments, offline use, system links and WCAG 2.2 AA design.
04
AI agent behind the app
6 to 10 weeks. One workflow, a pass sheet from your own test cases and the monthly model cost on the quote.
05
Bug-fix warranty
Included for 3 months after launch. Defects in the signed scope fixed at no charge.
06
Support and running
Monthly. A monthly report on crashes, use, updates and cost, plus Android updates and security patches. 3-month minimum, then 30 days’ notice.
Estimate your Android app in a minute
Pick what the first version needs: the starting picks are the repair-booking app priced below.
Included to start: Discovery, design, the Kotlin app, backend, basic push, closed test and Google Play launch. 6 to 8 weeks.
The scope of a first release
Our repair-booking example comes to £24,500 for 10 weeks, and the calculator above prices your own version. Discovery ends with one scope page like this, where every assumption says what happens if it fails.
Prices out of scope match the estimator tiles above, and you sign this page before the first build starts.
How much does an app cost in the UK?
The build plus a year of keeping the same repair-booking app running.
Worked example, excluding VAT
Fixed build price, discovery includedWeeks 1 to 10, the worked example above£24,500
+Months 1 to 3 after launchFixes under the 3-month warranty£0
+Months 4 to 12 after launch9 months of support at £750£6,750
=First year with us, excluding VAT£31,250
£37,500 with VAT at 20%. Not in this total, because the providers bill you direct: hosting, Google’s one-off developer account fee and any paid service the app calls, such as an AI model. Each is quoted at kick-off.
The first quarterly report on the example app
Months 1 to 3 after launch, measured against the same lines the build had to pass.
ExampleQuarterly report, repair-booking app, months 1 to 3AppAgentix
Measure
Months 1 to 3
Our line
Action
Crash rate, all users
0.31%
Under 0.5%
None
ANR rate
0.12%
Under 0.2%
None
Cold start, moto g04
1.8 seconds
Under 2 seconds
Pass after fix: 2.6 seconds in month 1, fixed in build 1.0.2
Crash rate, photo step on Android 14 tablets
0.8%
Under 0.5%
Open: fix planned for build 1.0.4 in month 4
Installs on Android 13
3.1%
The 2% to 5% band
Kept; weighed again next quarter against one test day a release
Fix builds shipped
1.0.1 to 1.0.3
Warranty
All under the 3-month warranty, at no charge
From month 4 the same report comes monthly under support, and an open row names the build that closes it.
Most app projects run late. More than 95% of ours are delivered on or before the agreed date, and yours can be next.
A first version (MVP) typically takes us 9 to 10 weeks, and the example app runs 10. Each stage names what you hold when it closes and who signs it.
Week12345678910monthly
01Discovery
02Design
03Builds 0.1 to 0.3
04Device and release testing
05Launch on Google Play
06Run and improve
01Closes end of week 2
Discovery
Your product owner signs the scope page.
You receive: Scope page, clickable prototype, device list, data map and one fixed quote.
02Closes end of week 3
Design
You sign the screens, checked on a small phone, a tablet and the largest text size.
You receive: Final screens and a component library you keep.
03Weeks 4, 6 and 8
Builds 0.1 to 0.3
You sign each backlog row below, or agree an open row and the build that fixes it.
You receive: Three builds installed on your own phone.
04Week 9
Device and release testing
Our tester and your product owner sign the report.
You receive: The device report below and the closed test results.
05Week 10
Launch on Google Play
You press release in your own Play Console. A personal account opened after 13 November 2023 first needs 12 or more testers opted in for 14 days running, so we start that test in week 8.
You receive: A live app and a staged-rollout plan for updates.
06Months 1 to 3, then monthly
Run and improve
Fixes are free for 3 months, then support keeps the app inside the gates.
You receive: A monthly report on crashes, use, updates and cost.
The sprint backlog for the example app
Each sprint ends with a build on your phone and one check that closes it.
Sign in with Google or email; the list of open slots
0.1
Sign-in works on all four test handsets
Pass
2, weeks 5 to 6
Book a slot; add a photo of the fault from the camera
0.2
A booking shows in the staff panel at the right time
Pass after fix: times showed an hour out after the clocks went back; fixed in 0.2.1
3, weeks 7 to 8
Staff panel with search; booking push
0.3
Notification permission asked after the first booking, never at launch
Pass
3, weeks 7 to 8
Search bookings by postcode
0.3
A postcode typed without its space still finds the booking
Open: fix booked for 0.3.1 in week 9
Builds reach your phone through Google Play internal testing. An open row names the build that fixes it, and you decide whether the sprint closes.
A change note, filled in
Mid-build, the repair firm in our example asks to take a call-out deposit, and nothing changes until this note is signed.
ExampleChange note 1: call-out depositAppAgentix
Line
Entry
Change
Customers pay a call-out deposit with Google Pay or card when they book
Work added
Google Pay or card checkout, 7 days of work
Price
Added to the fixed price once this note is signed
Time
Plus 1 week: launch moves from week 10 to week 11
Google Play billing
Not used: a repair visit is a physical service
Signed by
Your product owner and our delivery lead, before sprint 3 starts
Prices come from the estimator’s checkout option and our day rate, and an unsigned note is never billed. A change costs more the later you ask for it, because it reopens screens already built and tested, so every change is priced in writing before work starts.
The contract terms in short
You can stop at any payment point with 30 days’ notice, and you keep everything paid for up to then.
The release gates a build must pass
More than 95% of our projects are delivered on or before the agreed date. Each gate has a number and a fixed response: a build that misses one waits, unless you sign to release it with the miss written down.
Topic
Our line before release
What happens when a build misses it
Crash rate
Under 0.5% of users in the closed test
Release held; the largest crash group is fixed and the build re-run on all four test handsets
App not responding (ANR) rate
Under 0.2% of users
Release held; the frozen screen is traced, fixed and re-tested
Cold start on the low-memory phone
First screen in under 2 seconds
Release held; start-up work is cut or deferred until it passes
TalkBack on the core journey
Every control read out with a label
Fixed in the same build and heard again on the tablet
Largest text size
No text cut off on the core journey
Layout fixed and rechecked at that size
Our crash line is less than half of Google’s 1.09% bad-behaviour line, because a closed test sees far fewer sessions than a live app.
From Android Studio to Google Play
The tracks an Android build moves through before release.
01Kotlin build
02Internal test
03Closed test
04Play review
05Production
109
9:41
TRun 148 of 12 stops9 of 12 stopsETA4 min3 min2 min1 minArrived
9
22 Mill Lane3 parcels, side door
On the wayDelivered
7 Station RoadDelivered 10:02
103 Harbour StreetDue by 10:50
Proof of delivery10:21
Signed by M. AlderPhoto
RunMapScanMessages
The week 9 device report you receive
A filled report for build 1.0.0 of the repair-booking app, one row per real handset.
ExampleAndroid device test report, build 1.0.0AppAgentix
Role
Handset
Android version
RAM
Core journey
TalkBack
Large text
Notes
Older phone
Google Pixel 4a
Android 13
6 GB
Pass
Pass
Pass after fix
At the largest text size the sign-in button sat under the keyboard; layout fixed in this build and rechecked
Low-memory phone
Motorola moto g04
Android 14
4 GB
Pass after fix
Pass
Pass
Adding a photo restarted the journey when the camera closed; the screen now keeps its state
Current phone
Google Pixel 9
Android 16
12 GB
Pass
Pass
Pass
Also checked in dark mode and after an upgrade from the last test build
Tablet
Samsung Galaxy Tab A9+
Android 14
8 GB
Pass
Open
Pass
TalkBack skips the day labels in the tablet date picker; fix booked for build 1.0.1
Three makers. Android 13 is the lowest version tested and the minimum agreed in scope. Anything open names the build that fixes it, and you decide whether the release goes ahead.
Play Console set-up: who does what, and when
The account tasks for the example app. Yours stay yours, so the app never depends on a login held by your Android app development company.
Open the developer account in the firm’s name and pay Google’s one-off fee
You
1
Invite our engineers as users with only the rights they need
You
1
Create the upload key and keep it
You, with our engineer on a call
2
Set up internal testing and add your phones
Us
3
Set the target API level Google requires
Us
3
Name 12 or more closed testers, if your account needs a closed test
You
8
Draft the data safety answers from the data map
Us
8
Check and submit the data safety answers
You
8
Approve the store listing words and screenshots
You
9
Press release to production
You
10
We never ask for your Google password, and any task on your side we can walk you through on a screen share.
Each UK and Google Play rule, mapped to a screen
The same repair-booking app, rule by rule, with the exact screen or setting each one changes. Google prevented over 1.75 million policy-violating apps from being published on Google Play in 2025 (Google, February 2026).
RuleScreen or setting in the example app
01RuleUK GDPR storage limitation
Screen or setting in the example appFault photos deleted 90 days after the visit
02RulePECR marketing consent
Screen or setting in the example appAn unticked offers box on the sign-up screen
Past customers may fall under the soft opt-in, and every email still carries an opt-out.
03RulePECR storage and access rules, which cover apps
Screen or setting in the example appAdvertising tools stay off until the user agrees
Usage analytics has an off switch in Settings.
04RuleGoogle Play account deletion
Screen or setting in the example appSettings, then Delete account, plus a web link for deleting from outside the app
05RuleAndroid 13 notification permission
Screen or setting in the example appAsked on the booking confirmation screen
Never at first launch, so the reason is plain.
06RuleEquality Act 2010, section 29
Screen or setting in the example appA TalkBack label on every control of the booking journey
The data map behind the Play form
One row per field, written before the screens are built. The Play data safety answers are copied from it.
ExampleData map, repair-booking appAppAgentix
Field
Why the app holds it
Lawful basis
Kept for
Play data safety type
Name and email
Account and booking messages
Contract
Until the account is deleted
Personal info: Name, Email address
Home address
Sending the engineer
Contract
2 years after the last visit
Personal info: Address
Photo of the fault
The engineer brings the right part
Contract
90 days after the visit
Photos and videos: Photos
Offers email choice
Sending offers
Consent
Until withdrawn
Personal info: Email address
Crash reports
Finding and fixing faults
Legitimate interests
90 days
App info and performance: Crash logs
You set the retention periods with us in discovery; these are the example’s. Your data protection adviser gets the map with the build.
Who holds what on day one, and how you remove us
Topic
Holder on day one
The step that removes us, and how long it takes
Play Console and upload key
You, in your company name
Remove our users in Play Console: one step, the same day
Code and designs
Your repository; copyright passes as each invoice is paid
Remove our repository access: one step, the same day
Customer data
A cloud account you hold, under a data processing agreement
Ask for a full export: within 5 working days
Documentation and credentials
Kept in your repository as the build goes
Handed over within 5 working days of your notice
Our refund promise: if we do not deliver what the written scope promises, we refund what you paid for the undelivered work within 7 days. The same line sits in our terms.
How you pay for the example app
The repair-booking app, split into five payments. Each one falls due only when its trigger has happened.
Final screens; sign-in and open slots on your phone
The sprint 1 check passes
3, build 0.2
6
Booking and fault photo on your phone
The sprint 2 check passes
4, build 0.3
8
Staff panel and booking push on your phone
The sprint 3 checks pass, or you accept an open row
5, launch
10
Signed device report; the live app in your account
The app is live on Google Play
Total
10 weeks
Everything above
Each row above
A signed change note adds its price to the payment where its work lands, so change note 1 would be added to payment 4.
What our Android app developers refuse to do
Each refusal protects your app, your Play account or your users.
Hold your upload key or publish from a Play account of ours
Both stay in your name, as set out above.
Release a build that misses a gate without your signature
Ask for a permission the feature does not use
For example, contacts, SMS or background location in an app that never uses them.
Ask for notification permission at first launch
Skip the closed test when your account needs one
Add AI where a form, a rule or a search box does the job
AI brings a monthly model bill and testing of its own.
Start on a change before its change note is signed
Leave a control in the main journey that TalkBack cannot name
What a takeover audit looks like
ExampleTakeover audit, extractAppAgentix
Area
What we found
Verdict
Upload key
Held only by the previous agency
Fix in 1 day: Google resets it to a key you hold
Target API level
Below the level Google now requires, so updates are refused
Fix
Crash rate
2.3% in Android vitals, above Google’s 1.09% line
Fix the three largest crash groups
Permissions
Asks for contacts and location it never uses
Fix in 1 day: remove both
Payment screens
Card details typed into a web page inside the app
Rebuild as Google Pay or card checkout
Booking and account screens
Kotlin, with tests that pass
Keep
Sent within 10 working days of access. In the full audit, each row carries its price in days of work at our rate card. You pick the rows to act on, and each becomes a change note or a fixed quote.
When Android app development services are the wrong buy
Three numbers that tell us, as an Android app development company, that a native build is the wrong buy, and what we point you to instead. UK adults use an average of 41 apps a month on their smartphones (Ofcom Online Nation 2025). In StatCounter’s October 2026 figures, iOS holds 50.14% of UK phones. Android holds 49.85%.
Is a native Android build the right buy?
Ifyour whole budget for the first version is under our lowest MVP price
ChooseDiscovery on its own
In 2 weeks you hold a scope page, a clickable prototype and a fixed quote that any team can build from.
Ifyou need the app in users’ hands in under 6 weeks
ChooseThe clickable prototype from discovery
Our shortest MVP is 8 weeks, and a new personal Play account adds a 14-day closed test. The prototype can be shown at your event while the app is built.
Ifover 40% of your customers carry iPhones
ChooseFlutter, for both phones
Both phones fit inside the same MVP price, and you skip a second native app later at about 70% of the first.
Not sure what your app would cost? Send us the idea and get scope, timeline and a price range in writing within two working days.
The ten questions discovery starts with: users, the jobs they need done, systems to connect, rules, deadline and budget. Fill it in, attach nothing else, and the first call starts at the right place.
With us, an Android-only MVP costs £15,000 to £40,000, excluding VAT, and a full Android app takes 4 to 8 months. Our repair-booking example runs 10 weeks, paid in five parts, and the estimator above prices your own feature list.
Is Android app development free?
No: with us you pay one fixed price for the build, and the estimator above prices your own feature list. Publishing also has a cost: you open the Play Console account in your firm’s name and pay Google’s one-off fee yourself. In our repair-booking example, the Google Play launch in week 10 sits inside the fixed price.
Is Android development in demand in 2026?
Demand for your own app is the figure that matters, so check what share of your website visits comes from iPhones. Over 40%, our rule points to Flutter for both phones; under that, Android alone is a sound first build.
Which language is better for Android development?
We build native Android apps in Kotlin, and our rule picks it when over a quarter of your estimate sits in Android-specific tiles, such as a widget or barcode scan. Outside Kotlin, each of those tiles costs about 2 to 4 more days of work.
Is Flutter or Kotlin better?
Neither wins for every app. Our rule: an iPhone launch within 3 months of Android points to Flutter, while over a quarter of the estimate in Android-specific tiles points to Kotlin.
Does Google take 30% of in-app purchases?
Only on some UK sales, as of November 2026: auto-renewing subscriptions pay Google 10%. Other digital sales pay 20% when the buyer first installed or updated the app on or after 30 June 2026, or 25% for older installs. Google adds a 5% billing fee to each rate when its billing is used, so older installs still reach 30%. A physical service such as a repair visit must not use Google Play billing, so it is paid by Google Pay or card instead.
Can ChatGPT build an Android app?
It can draft screens and code, but it cannot hold a build to our release gates or hear TalkBack on a real tablet. Nor can it submit your data safety answers, because Google says only you hold that information. We use AI tools in our own work and show on the quote where they lower your price.
Is React Native still good in 2026?
Yes, for an Android app, when two or more React developers on your staff will own the code after handover. They can then make small changes in-house instead of buying Kotlin days from us. Without that team, our rule picks Flutter if iPhone must launch within 3 months of Android, or Kotlin if Android-specific tiles pass a quarter of the estimate.
How difficult is Android app development?
In our view, Android app development gets difficult because of the spread of phones and Android versions an app must work on. We keep a version once it holds over 5% of installs, and each version kept costs about one test day per release. A personal Play account opened after 13 November 2023 also needs 12 or more testers opted in for 14 days running.
Most app projects run late. Let’s make yours the one that ships.
More than 95% of our projects are delivered on or before the agreed date. About 60% of our clients come back for a second project.
What happens next
1We reply within 30 minutesEvery day of the year. A developer at our app development company, not a sales team, reads your brief.
2A 30-minute callWe ask about users, deadlines and the systems you already run.
3A written view in two working daysScope, timeline and a price range, yours to keep.
Thank you. Your brief is in.
A developer, not a sales team, reads it. We reply within 30 minutes, from info@appagentix.co.uk.
We use cookies to run this site and, with your permission, to understand how it is used. Cookie policy · Privacy policy
Most app projects run late. Let’s make yours the one that ships.
More than 95% of our projects are delivered on or before the agreed date. About 60% of our clients come back for a second project.
What happens next
1We reply within 30 minutesEvery day of the year. A developer at our app development company, not a sales team, reads your brief.
2A 30-minute callWe ask about users, deadlines and the systems you already run.
3A written view in two working daysScope, timeline and a price range, yours to keep.
Our patients needed the portal in their pocket: requesting visits, reading test results, reordering medicines and messaging their care team. AppAgentix built the Android app on our Epic MyChart system, careful where it matters: secure sign-in, no clinical detail on the lock screen, and patients choose what fitness data they share. The app has passed 50,000 downloads with 4.4 stars from over 750 reviews, and every release was tested before it reached our patients.