Kotlin, Jetpack Compose, Play Console
Android, built for the phones your customers actually own.
Android is not one device. It is a decade of hardware, four active OS versions, three manufacturer battery managers and a store with policies that change every year. We build for that reality: Kotlin and Compose, tested across the range in your analytics rather than on one flagship, and released through staged rollout so a bad build reaches a fraction of users rather than all of them.
Technologies
01Capabilities
Compose, not a decade of XML
Jetpack Compose with Material 3 and a real design system, so a screen is written once and adapts to phone, foldable and tablet instead of being three layouts that drift apart.
Background work that survives the OEM
Samsung, Xiaomi and Huawei each kill background processes their own way. We use WorkManager with the constraints Android actually honours, and test that sync still runs after the phone has been idle overnight.
Play Console handled properly
Internal, closed and open testing tracks, staged rollout with a halt threshold, Play App Signing, and the Data safety form filled in from what the app really does rather than from a template.
Target API upgrades on schedule
Google raises the required target API level every year and delists apps that fall behind. We track it as maintenance work, not as an emergency the month the deadline lands.
02Scope
What is included
- Native Android apps in Kotlin and Jetpack Compose
- Migration from Java, XML layouts or an abandoned hybrid app
- Offline-first storage with Room and conflict-aware sync
- Push notifications through Firebase Cloud Messaging
- Play Billing for subscriptions and in-app purchases
- Foreground services, WorkManager and Doze-safe scheduling
- Phone, foldable, tablet and Android Auto layouts
- Play Console setup, testing tracks and staged rollout
- Data safety declarations and permission review
- Annual target API level upgrades and OS compatibility work
- Crash reporting, ANR triage and performance profiling
03Release
How a build reaches the Play Store
Android lets you release gradually, which is its real advantage over the alternative. We use all of it.
Internal testing
Up to a hundred testers, available minutes after upload. Where the team and the client check a build before anyone outside sees it.
Closed track
A named group of real users on real devices. This is where OEM battery managers, older OS versions and odd screen sizes surface — not in the studio.
Staged rollout
Released to 1%, then 5, 10, 25, 50, 100, watching crash-free rate and ANRs at each step. A regression stops at the next gate instead of reaching everyone.
Halt and patch
A rollout can be halted mid-flight, which is the point of doing it this way. The fix ships as a new staged release rather than as a panic.
04The unglamorous part
What actually breaks Android apps
Almost never the feature work. What breaks Android apps in the field is the platform underneath: a background sync that a manufacturer silently killed, a permission model that changed between OS versions, a WebView update that broke a screen nobody touched, or a target API bump that forced a storage rewrite.
So we plan for it. Storage goes through the scoped APIs from the start rather than being migrated under deadline. Notification permission is requested at a moment that makes sense to the user, because on Android 13 and later it can simply be refused. Background work states its constraints and is verified after a real overnight idle, not in a simulator.
And the app is tested on the devices in your analytics. If a third of your users are on a four-year-old mid-range phone with 3GB of RAM, that phone is in the test set — a build that only ever ran on a current flagship has not been tested.
05Questions
Frequently asked questions
Native Kotlin or React Native for Android?
If the app is also going to iOS and the interface is mostly standard, cross-platform usually wins on cost — one team, one codebase, roughly half the build. Native Kotlin earns its keep when you need deep platform integration, heavy background work, tight performance on low-end devices, or the newest platform features on the day they ship. We build both and will tell you which your requirements actually justify.
How long does Google Play review take?
Usually hours to a few days for an update, longer for a first submission or after a policy-sensitive change. It is materially faster and more predictable than the App Store, which is why we often ship Android first and use it to shake out issues before the iOS submission.
What is the Data safety form and why does it matter?
It is Google’s required declaration of what data your app collects, shares and how it is protected — shown on your store listing. It has to match what the app and its SDKs actually do, including analytics and advertising libraries. A mismatch gets apps removed. We fill it in from an audit of the network traffic rather than from what the SDK documentation claims.
Which Android versions should we support?
We set the minimum from your own analytics, not from a general recommendation. For most consumer apps that means the last four or five major versions, which covers well over ninety per cent of devices. Supporting one version further back can double the testing surface for a very small share of users, so it is a decision worth making with numbers.
Can you take over an existing Android app?
Regularly. We start with an audit — target API level, dependency versions, crash-free rate, ANR rate, build reproducibility and store policy standing — and give you a written risk list. Apps that have fallen behind the target API requirement are the most urgent, because Google eventually hides them from new users.
06Nearby
Related services
Mobile App Development
React Native and Flutter apps for iOS and Android, plus installable progressive web apps — connected to the same backend and ERP as the rest of your systems.
DevelopmentiOS App Development
Native iOS apps in Swift and SwiftUI — built to Apple’s guidelines and submitted with the privacy declarations and review evidence that get an app approved the first time.
DevelopmentNext.js & React Development
Server-rendered Next.js applications and headless frontends — the modern web stack, built for Core Web Vitals, indexability and conversion rather than for a framework demo.
What we do
Android App Development
Native Android apps in Kotlin and Jetpack Compose — built for the device range your users actually hold, and shipped through Play Console without the release surprises.