Hire Android App Developers who ship to Google Play
In-house Kotlin developers for consumer Android apps: Jetpack Compose screens, Play Billing subscriptions and releases through Play Console. You interview the developer before you sign, work starts within 24 hours of signing, and the app stays listed under your own company's Play Console account.
On this page
Send us a short brief on the app and its users, meet the Kotlin developer we put forward, and sign once you are satisfied. The developer starts within 24 hours of the signature, which in practice is the following working day. They are on our staff, build screens in Jetpack Compose, and release through a Play Console account your company owns.
What an Android hire includes, and what stays in your name
The developer you hire through us is already employed here, not someone recruited after your deposit clears. The person you question in the interview is the person who opens pull requests in your repository and sends builds to your testers. If the interview goes badly, you stop there, before anything is signed.
A consumer Android app is more than screens. It needs sign in, an API, push notifications, often a subscription, and a store listing that Google reviews. When the work reaches the server, Node.js and Python developers sit on the same team, and on the builds we deliver, our QA team tests each one before it gets to you. Apps for company devices and kiosks have their own page: Android developers for business devices.
| Part of the hire | What it means on an Android app |
|---|---|
| A Kotlin developer on our staff | Employed by Digital Heroes and writing native Kotlin, the language Google recommends for new Android apps |
| A meeting before the contract | You question the person who will commit the code, with no stand-in from sales |
| Day one is the next working day | Work begins within 24 hours of the signature |
| A two-way NDA | A one-page agreement, signed as soon as a scoping call is in the diary and before designs or code change hands |
| Your Play Console and your repository | Your company is the account owner; our developer joins as a user with the permissions you grant |
| Testing before your testers see it | When we deliver the build, on a dedicated team or a fixed-scope project, our own QA people test it first |
What a consumer Android developer works with every day
A consumer app is judged on its store listing and its first minute of use, so the stack should be the one Google itself builds for. Google has called Android development Kotlin first since Google I/O 2019, and it reports that Android apps containing Kotlin code are 20 percent less likely to crash.
For the interface, Google describes Jetpack Compose as Android's recommended modern toolkit for native UI. Our Android app development practice writes new screens in Compose and keeps XML layouts for maintaining older code. The table lists what the developer should handle, and what to ask them to show you as proof.
| Area | What it covers in a consumer app | Ask the candidate to show |
|---|---|---|
| Kotlin and coroutines | Null safety, and network and database calls that never freeze the screen | A recent pull request from real work, not a tutorial repository |
| Jetpack Compose and Material 3 | Screens, theming, dark theme, and layouts that adapt to phones, tablets and foldables | A screen they built, and where its state lives |
| Local data and background work | Room for offline caches; WorkManager for uploads and syncs that must finish after the app closes | A time they chose WorkManager over a plain coroutine |
| Google Play Billing | Subscriptions and one-time purchases, acknowledged in time and checked on your server | How a purchase travels from the phone to your backend |
| Sign in and security | Credential Manager for passkeys and Sign in with Google, and short-lived tokens | What their last app stored on the phone, and what it did not |
| Release and quality | App Bundles, Play App Signing, staged rollouts, and crash and ANR rates in Android vitals | A rollout they halted, and what they found |
The kinds of consumer app this covers are the familiar ones: subscriptions and content, marketplaces and bookings, fitness and habit trackers, and the companion app to a web product. If your app also has to run on iPhone within the year, read the section on when a native Android developer is the wrong hire before you decide.
Google Play's rules in 2026, and what each one does to your plan
Much of the wait in a first Android launch is policy and process rather than code. A developer you hire should know every row below before the first sprint, because each one moves a date. We read each requirement on Google's own help pages on 17 October 2026; the sources section links them all.
| Requirement | What Google asks | What it means for your plan |
|---|---|---|
| Account type | An organization account needs a D-U-N-S number, which Dun & Bradstreet issues free of charge | Open the account as your company, not as a person, and request the number early |
| Testing on new personal accounts | Accounts opened by an individual after 13 November 2023 need a closed test of 12 or more testers, opted in for 14 consecutive days; Google says its review of the production application usually takes seven days or less | Allow about three weeks between a finished build and a public listing on a personal account |
| Target API level | Since 31 August 2026, new apps and updates must target Android 16 (API level 36), with extensions to 1 November 2026 on request | An app nobody has touched for a year needs upgrade work before its next update |
| Android App Bundle | New apps have had to publish as an App Bundle since August 2021 | The developer uploads an .aab file and Google builds the version each phone installs |
| 16 KB memory pages | Apps targeting Android 15 or higher must support 16 KB page sizes on 64-bit devices; from 1 February 2027, updates without that support cannot be released | Any native code in the app, yours or an SDK's, has to be checked and rebuilt where needed |
| Data safety form | Every app on a closed, open or production track declares the data it collects and shares, including through SDKs, and links a privacy policy, even when it collects nothing | List every SDK in the app before launch, because each one changes the answers |
| Account deletion | An app that lets people create an account must let them delete it inside the app and through a web link | Build the deletion flow into the first version, not after a rejection |
| Play Billing Library | Since 31 August 2026, new apps and updates must use version 8 or later, with extensions to 1 November 2026 | Subscription code written against an older library needs an upgrade before the next release |
After launch, each update can go out as a staged rollout to a share of your users, and Google lets you halt it if something breaks. Staged rollouts work for updates only, never for the first release, which is why the closed test has to be thorough.
Android vitals then scores the result, and Google says core vitals affect how visible an app is on Google Play. Its bad behavior thresholds are a user-perceived crash rate of 1.09 percent and an ANR rate of 0.47 percent averaged across devices, or 8 percent for either on any single phone model. A developer worth hiring checks those numbers after every rollout, not only when reviews turn bad.
Subscriptions and in-app purchases on Google Play
Many consumer apps earn through a subscription or one-time purchases, and billing is where a small coding mistake turns straight into refunds. Google refunds and revokes any purchase the app has not acknowledged within three days, so a payment that never reaches your server is a payment you lose.
- The paywall and the purchase flow, built on Play Billing Library 8 or later, with the products set up in Play Console.
- A check on your server for every purchase, so access is granted by your backend and not by the phone alone.
- Acknowledgement inside three days, including the case where the user closes the app halfway through.
- Restores on a new phone, so a subscriber who changes devices keeps what they paid for.
- Refunds and cancellations from your backend, where Google advises revoking a rejected purchase.
Google's fee comes out of each sale. For users in the US, the UK and the European Economic Area, Google lists a 10 percent service fee on auto-renewing subscriptions, plus a 5 percent billing fee when the purchase runs through Google Play Billing; that structure took effect there on 30 June 2026. In markets where it has not yet rolled out, subscriptions carry 15 percent. Price your plans with those numbers in, not after.
Three ways to bring a Kotlin developer onto your app
Pick the model by who will review the code and own the release, not by the monthly figure alone. Each model is billed differently, and each puts a different person in charge of what ships.
- A developer inside your team, billed monthly. One Kotlin developer joins your standups and your repository and works to your product lead's priorities. It fits when someone on your side can review Android code and approve releases.
- A dedicated Android team, billed monthly. A lead, developers and QA own the app or a slice of it against your roadmap, and our lead answers for delivery. It fits a roadmap that runs for months with no mobile lead of your own.
- A fixed-scope app build, one price. It opens with two weeks of discovery, paid for separately, which ends with either a fixed price against a written scope or a recommendation to buy an existing product instead.
Only the first model starts inside 24 hours. Assembling a whole team takes longer, and our dedicated development team page covers how that works. Not yet sure Android alone is right? All four mobile stacks we staff are set side by side on our mobile app developer hiring page.
How the developer is vetted, and the checks to run yourself
Our vetting is employment, not a test passed once on a marketplace. The developer works for us, to the engineering standard our CTO, Divyansh Singh, owns, and on the builds we deliver, our QA team tests each one before you see it. We do not list developers by name on this page. The interview is where you meet the developer we have in mind for your app, and a no from you ends it there.
The checks that matter most are the ones you run. Ask to see an app on Google Play the developer has worked on, or a walk-through of one under NDA. Then pay for a trial of two or three days before any long contract: one small feature taken through review and onto your internal testing track tells you more than a CV.
The company behind the developer can be checked too. On Clutch, Digital Heroes holds 5.0 from 66 verified reviews (checked 13 October 2026). Dun & Bradstreet lists it under DUNS number 650878346, and the UN Global Marketplace lists it as a Tier 1 supplier. Our mobile engineers work from the Delhi headquarters, and the Sydney office has iOS and Android engineers.
From signature to a first feature in your testers' hands
The contract is signed one day and the developer is at work the next, but that first day is all logins. Missing access is the usual reason a first week runs slow, so gather four things in advance: the code repository, the design files, a company Play Console account, and the handful of phone models your users actually own.
- Day 1: logins and a local build. You invite the developer to the code and to Play Console with rights on your app only, and pass over the backend project and a test account. By evening the app should run on an emulator and on a physical phone, with a list of whatever is still missing.
- Days 2 to 5: the release path, proven small. Pick a minor bug. The developer fixes it, gets it reviewed, signs the bundle with your upload key and puts it on the internal testing track, which Google says normally reaches testers within seconds. A broken step shows up now, on a one-line change.
- Week 2: real backlog work. A feature small enough to finish in five working days, tried on the phone models you named, with Android vitals checked before the build goes beyond your internal testers.
- Day 14: a review in writing. One page from the developer on what landed, what slowed it, and which changes to builds, tests or access would speed up week three.
If the app is already live, Reach and devices in Play Console breaks your installs down by Android version, memory and screen, which tells the developer which phones to test on first. The free software project timeline calculator converts your own hours and headcount into a schedule.
Six questions to ask in a Kotlin interview
Android developers who have only studied the platform interview well on syntax. These questions are about what happens on real phones after launch, so the answers come from shipping. Ask every candidate the same six, ours included, and write the answers down side by side.
- "Android kills the app in the background while a user is halfway through checkout. What do they see when they return?" Listen for saved state restored from the ViewModel and the local database, not a flow that starts again from the beginning.
- "When do you use a coroutine, and when a WorkManager job?" A good answer ties a coroutine to work a screen needs, and WorkManager to work that must finish after the app closes, such as an upload.
- "A Compose list stutters on scroll. Where do you look first?" Expect recomposition counts, stable item keys, heavy work moved off the main thread, and a test on a release build rather than a debug one.
- "How does a subscription purchase reach our server, and what if it is never acknowledged?" The candidate should know Google refunds it after three days, and should verify every purchase on the backend.
- "The ANR rate climbs right after a release. What do you do in the first hour?" Halt the staged rollout, read the ANR clusters in Android vitals, and find whatever blocks the main thread.
- "Where does the upload key live, and what happens if it is lost?" The right answer puts it in your company's secret store and knows Google can reset a lost upload key under Play App Signing.
Four red flags in an Android candidate
- Nothing they can show on Google Play. Confidential work is normal, but a developer should be able to walk you through at least one app they released.
- AsyncTask in new code. Android deprecated it in API level 30 and points developers to Kotlin concurrency instead, so seeing it in recent work means old habits.
- Passwords kept on the phone. Google's security guidance says not to store user IDs and passwords on the device, and to use short-lived tokens.
- A launch date with no closed test in it. On a new personal account, 14 days of closed testing is a rule, not a choice, and a plan that skips it will slip.
What it costs to hire Android app developers, by public data
There is no Digital Heroes price list on this page. We quote one developer by the month after a scoping call, when the hours and the work are clear. Below is public market data instead, so that every quote you collect, ours among them, can be checked against figures no vendor wrote.
On its cost page for Android app developers, Upwork gives a median of $15 to $35 an hour. Those rates come from historical contracts around the world, and Upwork notes that client and freelancer negotiate the real figure. Multiply by roughly 160 working hours and one full-time freelancer costs $2,400 to $5,600 a month, with no code review or device testing included.
An employee of your own in the US costs more. US software developers earned a median $135,980 a year in May 2025, according to the Bureau of Labor Statistics. That is about $11,300 a month in salary alone, with benefits, payroll taxes, equipment and months of recruiting still to add.
| Route | Public figure | What the figure leaves out |
|---|---|---|
| Freelancer on Upwork | $15 to $35 an hour, median, worldwide contracts | Code review, device testing, and a replacement if the freelancer disappears |
| Your own employee in the US | $135,980 a year, median wage for software developers | Benefits, payroll taxes, equipment and recruiting time |
| Developer from Digital Heroes | Quoted monthly after a scoping call | Ask what any quote includes; on the builds we deliver, our own QA team tests each one |
Want a figure for a finished app instead of monthly time? Our mobile app cost calculator treats native Android in Kotlin as its baseline. A focused MVP comes out at $40,000 to $80,000 and takes 3 to 5 months; a mid-complexity business app, $90,000 to $180,000 across 5 to 8 months. Building natively for both Android and iPhone multiplies the band by 1.7 to 1.9.
Google charges a one-time US$25 when you open a Play Console account, and takes its service fee on each sale, as the billing section shows; neither is part of any developer's rate. The free in-house vs agency cost calculator prices identical project hours three ways: salaried, agency and freelance.
One mobile build on show, and its limits
AirTrainr connects athletes with sports trainers, and its athlete and trainer mobile apps are ours: React Native and Expo on the phone, Supabase behind it. Two kinds of user, search, bookings and messages between them make a common shape for a consumer app. The client allowed us to show the work; we publish no figures for it.
It is a cross-platform build, not a native Kotlin one, and we have not yet published a native Android client case on this site. So ask, in the interview, to see the proposed developer's own Android work, under NDA where it has to be. A developer who cannot show any is the first red flag above, whoever employs them.
Who owns the app, the keys and the listing
Our MSA hands you the code, designs and assets built for your project once it is paid in full, while tools and libraries we had beforehand remain ours. On Android, ownership also sits in three places a contract cannot reach unless you set them up: the repository, the Play Console account and the signing keys.
Make your company the Play Console account owner. Google gives the owner full access and makes it the only role that can link a payments profile to sell paid apps. Add our developer as a user with access to your app alone; Play Console also lets you set a date on which that access expires.
With Play App Signing, Google holds the app signing key that signs what users install, and you hold the upload key the developer signs each bundle with. Google can reset a lost or leaked upload key; an app signing key you manage yourself and lose cannot be reset. Keep the upload key in your company's secret store, never on one laptop.
The contracting party is whichever entity your MSA names, Digital Heroes Technologies Pvt Ltd in India or Digital Heroesco LLC in the US, and New York law usually governs US work. Each entity and office, and how to verify it, is listed on our custom software development company page.
Weekday messages to the New York office between 9 AM and 6 PM Eastern get an answer the same day. Engineers in Delhi and Lucknow keep hours that overlap New York's, Delhi and Sydney share production emergencies around the clock, and a message sent after hours is picked up within one to two hours. The free time zone planner shows the overlap from your city.
When a native Android developer is the wrong hire
Because we staff four mobile stacks, selling you Kotlin when another stack suits you better gains us nothing. These are the cases where we would say so on the first call.
- The iPhone app is due within the year. A single codebase for both stores is normally cheaper to build and to maintain, and React Native is the default our CTO chose for apps that run on both. Flutter suits a heavily branded interface.
- The app is a website in disguise. If it is mostly forms and content, a progressive web app may do the job with no store listing at all; our guide to native app vs PWA walks through the choice.
- The job is measured in hours. One bug fix or one library upgrade on an app you otherwise run yourself is a small contract, and a monthly hire is more than it needs.
- Only the hourly rate matters. A marketplace freelancer will usually come in under any company with staff, review and QA behind each developer, ours included.
Not sure the app should exist yet? Test the idea with the free app idea validator before anyone writes code. For an iPhone-only product, see our iOS app development page.
Where the numbers come from
We read each of these pages on 17 October 2026, and every outside number on this page traces to one of them. Links go straight to the publisher.
- Play Console Help, app testing for new personal developer accounts: the closed test, the production review and internal builds.
- Play Console Help, choose a developer account type: the free D-U-N-S number an organization needs.
- Play Console Help, target API level requirements: API level 36 and the extension date.
- Android Developers, About Android App Bundles and Support 16 KB page sizes: the bundle rule and the 16 KB date.
- Play Console Help, Data safety section and account deletion requirements: the form, the privacy policy and deletion.
- Android Developers, Play Billing Library deprecation, integrating Play Billing and Play Console Help, service fees: version 8, the three-day rule and the fees.
- Play Console Help, staged rollouts and Android Developers, Android vitals: rollouts and the crash and ANR thresholds.
- Play Console Help, Play App Signing and account users and permissions: the two keys, the owner role and access expiry.
- Android Developers, Kotlin first, Jetpack Compose, AsyncTask reference and security tips: the crash figure, Compose, the deprecation and credential storage.
- Upwork, Android App Developers cost and Bureau of Labor Statistics, Software Developers: the hourly median and the annual wage.
- Android Developers, distribution dashboard: Reach and devices in Play Console.
- Android Developers, Gemini in Android Studio: Google's coding assistant and its free tier.
Questions buyers ask before an Android hire
How much does it cost to develop an app for Android?
Scope decides it. For a native Android build, the focused MVP band in our mobile app cost calculator is $40,000 to $80,000, with a 3 to 5 month timeline. A mid-complexity business app, with payments, notifications and an admin dashboard, lands at $90,000 to $180,000 across 5 to 8 months. Google adds a one-time US$25 for the Play Console account.
How much does it cost to hire an app developer?
On Upwork, the median for Android app developers is $15 to $35 an hour on past contracts worldwide, or roughly $2,400 to $5,600 for a full-time month. Employing someone in the US costs far more, since half of US software developers earned over $135,980 in May 2025, by Bureau of Labor Statistics figures, and that is before benefits and recruiting. We price our own developers by the month, after a scoping call.
Can ChatGPT create an Android app?
It can write Kotlin code and explain errors, and Google ships its own assistant, Gemini in Android Studio, which generates code, helps mock up Compose screens, fixes Gradle build errors and analyses crashes, with a free tier for individuals. What no assistant does for you is own the release: the Play Console setup, the Data safety answers, the closed test, the signing keys and the crash rates after launch. Someone accountable still has to do that.
How much does it cost to pay someone to build a mobile app?
It depends on whether you pay for hours or for a finished app. Hours run from the Upwork median of $15 to $35 for Android work upward. For a finished app, the calculator's MVP band of $40,000 to $80,000 covers one native platform; native apps for both Android and iPhone multiply that by 1.7 to 1.9, which is why one cross-platform codebase often costs less.
Where can I find and hire app developers I can trust?
Three places: a freelance marketplace, a referral from someone who has shipped an app, or a company with developers on staff. Whichever you choose, trust comes from checks, not the platform: an app on Google Play the developer can walk you through, a conversation with whoever will actually write yours, a short paid trial, and your own company holding the repository and the Play Console account from day one.
How quickly can an Android developer start?
The day after you sign, as long as that is a working day; the promise is a start within 24 hours. Expect day one to go on getting into the repository, your Play Console, the backend and a test account. A full team needs longer to form, and a fixed-scope project begins with two weeks of discovery instead of coding.
Should I hire a Kotlin developer or a cross-platform developer?
Hire Kotlin when the app is Android only, or leans on Android features such as background work, widgets or deep system integration. Hire React Native or Flutter when an iPhone version is planned within the year, since a single codebase covers both stores. We staff all three, and React Native is the stack our CTO picked as the default when an app must run on both.
Who owns the code, the signing keys and the Play Store listing?
Your company does, if it is set up properly. The MSA assigns the work to you once it is paid in full. Make your company the Play Console account owner, the one role able to link a payments profile, and add our developer as a user. Google keeps the app signing key under Play App Signing, and the upload key goes in your own secret store.
Last reviewed .
Describe the app, then interview the developer
Start with three facts: what the app does, who uses it, and whether it is on Google Play yet. A 30-minute call with Digital Heroes comes first, then an interview with the Kotlin developer we suggest. Sign after that and the work begins the following working day. Nothing on the call binds you. Book a call to meet an Android developer.
Why work with Digital Heroes
115 people across five studios in New York, Delhi, London, Sydney and Lucknow, shipping ecommerce, web, software and mobile work for founder-led brands. Senior engineers only, no account-manager relay, and the same team from kickoff to launch.
- Shopify Select Partner, as listed in the Shopify Partner Directory
- Tier 1 registered supplier on the United Nations Global Marketplace, which requires audited company documentation
- Top Rated Plus on Upwork, the bracket for the top 3% of talent by client outcomes
- 397 public five-star-weighted reviews across four Fiverr gigs, from clients in 36 countries
- DUNS verified business, No. 650878346, so procurement can check us before signing
- Listed by Clutch in Top 1000 Global B2B Companies and Top Web Designers 2024
- Verified profiles on GoodFirms, DesignRush, Digital.com, AppFutura and TopDevelopers
- 2,000+ brands built across 40+ countries, with $50M+ in client revenue scaled
More from Divyansh.
Chief Technology Officer · Lucknow · 50 posts on the site
Published .
