What we do
Tools
Industries
Department
How we workLet's talk →
Home/Android Developer
Android Development

Hiring an Android Developer? Settle Who Owns the App Before the First Build

Most of the cost of an Android app is the screens and the systems behind them. Most of the risk is elsewhere: whose Google account it's published from, how it gets onto your team's phones, and whether anyone tested it on the five-year-old Samsung your drivers carry instead of the developer's Pixel. Sort those out first and the build goes better.

How the app will reach your team's phones

Decide this before anyone writes code. It changes which accounts you need, what Google requires before launch, and how updates arrive.

Who uses the app How it gets onto phones What that means in practice
Customers or the public A public listing on Google Play Register the developer account as an organization, which needs your company's D-U-N-S number. A new personal account must first run a closed test with at least 12 testers for 14 days in a row before Google allows production; organization accounts skip that.
Your own staff, on phones the company manages A private app through managed Google Play Published from Play Console to your organization only, never shown in the public store, and installed by your device management tool. An app can't be public and private at once, and private apps can't be sold.
A pilot with a handful of drivers or techs Play Console's internal or closed testing tracks Testers get updates through Play like any other app, so the pilot runs on real phones without a public launch. Plan the pilot from the start, because the public route may require it anyway.
An APK file sent round by email or a download link Avoid it for anything staff rely on No automatic updates, every phone has to allow installs from unknown sources, and nobody can say which version each person runs.

Six things that belong in your company's name, not the developer's

Each one takes minutes at the start. Recovering any of them after a developer has gone can take weeks, or not be possible at all.

  • The Google Play developer account

    Google does let apps move between developer accounts, but the transfer goes through the account that holds the app. If the person who owns it won't reply, you can't push updates or answer a policy notice. Create the account under your business and add the developer as a user.

  • Access to app signing

    Play App Signing keeps the key that signs your app with Google. The developer uploads with a separate upload key, which the account owner can get reset if it's lost. That only helps if the account owner is you.

  • The Firebase project

    Push notifications and crash reports usually run through Firebase. A project created in the developer's own Google account takes those with it when they leave.

  • The Google Cloud billing account behind map and location keys

    Apps that show maps or routes call Google APIs that bill to a card. If that card is the developer's, the map can stop working the day they cancel it.

  • The source code repository

    Not a zip file at the end. A repository your company owns, with the history of every change and the steps to build the app written down.

  • The logins the app uses to reach your CRM or inventory system

    Use a dedicated integration account with its own credentials, not someone's personal login. Then nothing breaks when that person leaves or changes their password.

Bugs your developer's test phone won't show

Android runs on thousands of phone models from dozens of makers. Field apps meet the hard ones first: older phones, rugged handhelds and dead zones.

Background updates stop on some brands

How you'll know: Location or job status updates arrive fine on one model and stall on another as soon as the screen goes off.

Fix: Several manufacturers add battery savers on top of Android's own that stop background work. Use Android's scheduling tools (WorkManager) as intended, test on the actual models, and set the battery exemptions through your device management.

The app assumes a signal

How you'll know: A tech fills in a job in a basement, taps Save, and the work disappears or the app hangs.

Fix: Save everything on the phone first and send it when the connection comes back, with a visible count of anything still waiting to upload.

The minimum Android version doesn't match your fleet

How you'll know: A few older phones can't install the app at all, or features quietly fail on them.

Fix: List the models and Android versions your team really carries before the developer picks a minimum version. Replacing a few phones can be cheaper than supporting very old ones.

Rugged scanners behave differently from a phone camera

How you'll know: Barcode scanning works in testing with the camera, then the warehouse handhelds' built-in scanners don't fill the field.

Fix: Get one of the real devices to the developer early. Built-in scanners usually hand scans to apps through the maker's own software, which needs its own setup.

Crashes nobody reports

How you'll know: Staff restart the app and carry on, so the office never hears about it.

Fix: Check Android vitals in Play Console, which shows crash and freeze (ANR) rates by device model, and add crash reporting so problems arrive with the phone model attached.

Questions people ask

If a freelancer built the app under their own developer account, is that a problem?

It can be a serious one. If they stop replying, you may not be able to ship updates, answer a Google policy notice, or show that the listing is yours. Google has a process for moving apps to another developer account, but the request has to come from the account that holds the app, so ask for the transfer while they're still answering.

Do you build for iOS too, or Android only?

Both. Where the app is mostly forms and lists, one cross-platform codebase usually covers iOS and Android. Where it leans on scanners, background location or other hardware, native Android in Kotlin is often the safer choice. See our iOS developer and Flutter developer pages for the other routes.

Our app needs to talk to our CRM or inventory system. Is that a bigger job than a standalone app?

Usually, yes, and it's most of what we're hired for. The connection to your systems, plus working offline and catching up later, is normally where the time goes, not the screens. We scope what the app reads and writes before anything else.

What does a free quote actually cover?

We find out what the app has to do, who uses it, which phones they carry and which systems it talks to. The quote prices the screens, the connections to your systems and offline sync as separate lines, so you can see where the money goes and compare it line by line with any other estimate.

Kotlin or Java for a new Android app?

Kotlin. Google has recommended Kotlin for Android since 2019, and its current tools and samples assume it, including Jetpack Compose for building screens. Java still runs fine, and older apps and many libraries are written in it, so an Android developer should be able to read both. Our Java developer page covers Java work outside Android.

What should someone learning Android development focus on?

Kotlin, Jetpack Compose, and how Android handles background work and permissions. Then publish one real app through Play Console's testing tracks, because the account, signing and release steps are part of the job that courses tend to skip. Experience with a real backend API counts for a lot with employers.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.