Native Android app development
Kotlin and Jetpack Compose. Target Google Play and regional alternatives (RuStore, AppGallery).
Updated
A native Android app in Kotlin for Google Play and regional stores: design, development, release and updates for new Android versions. Timeline: 21 days. Priced after a short brief.
What's included
- Kotlin + Jetpack Compose
- Backend API integration
- Push via FCM or regional PNS
- Google Play Billing or direct payments
- Material You design
- Multi-store distribution
- Tablet and foldable adaptation
A native Android app built in Kotlin and Jetpack Compose. We make apps that work equally well in Google Play and in alternative stores such as RuStore, NashStore and Huawei AppGallery. That matters when part of your audience can't install apps from Google Play, whether because of their phone (Huawei devices without Google services) or their country (many users in Russia). We plan for multiple stores from the start instead of reworking the build for each one at the last minute.
Who it's for
- Companies that need an Android app for their customers alongside, or instead of, an iPhone app.
- Businesses with users in Russia, where RuStore distribution and push without Google services are often required.
- Products used on a wide range of devices: budget phones, tablets, foldables, corporate devices.
How we work
- Brief and prototype. We go through the scenarios, your audience's devices and the requirements of each store, then build a screen map and prototype to agree the logic before development.
- Design. Material You or your brand guidelines, your choice. We account for the variety of Android devices: screen sizes, pixel densities, foldables.
- Development in iterations. Kotlin, Jetpack Compose, MVVM with Coroutines and Flow. Each sprint ends with a build you can install on your phone.
- Integrations. We connect your backend, push through FCM for Google Play and through the store's own push service for devices without Google services, and payments suited to each store.
- Store publication. We prepare AAB and APK builds, set up the listings and go through moderation in Google Play and the other stores on the agreed list.
- Handover. You get the source code, signing keys and access, and we agree on an update plan.
What you get
One app published in several stores, which means wider reach without duplicate development. You get the source code in your repository, the signing keys (you must never lose them, or you can't release updates) and CI that builds a variant for each store. Push works even where there are no Google services: FCM in Google Play, RuStore push or Huawei Push Kit on devices without GMS. Payments use Google Play Billing in Google Play and direct gateways in alternative stores. Analytics and crash reporting are in place from the first release. Background work follows the Android 14+ rules for foreground services; otherwise the system kills it. On request we adapt the interface for tablets and foldables, or build versions for Android Auto, Wear OS or Android TV if they're part of your scenario. For corporate devices, a direct APK with auto-update is sometimes more practical than a store.
Timeline and cost
The reference point is 21 days for a medium-sized app integrated with an existing API. Publishing to several stores adds time for preparing and moderating each one. Complex scenarios such as offline mode, sync and background services are estimated separately after the brief. Before every release we test on real devices from different manufacturers and with different screen sizes.
Cost is estimated after a short brief. It depends on the number of screens and features, the list of stores (each has its own requirements), whether the backend exists, and add-ons such as tablet layouts or Wear OS.
Example
For example, for a company whose app has to work for all its customers, including people with phones that have no Google services, we would develop once and, at the publishing stage, build a variant for each store with the right push and payments. Google Play gets FCM and Google Play Billing; RuStore gets RuStore push and payment through a Russian gateway such as YooKassa or SBP. Background tasks are declared according to Android 14 rules. The client ends up with one codebase and a presence in several stores, not a separate hand-made build for each.
What we need from you
- A description of the task, and the API if one already exists. The screen map and prototype we build together.
- Developer accounts in the stores you need, registered to your company. We'll help with registration.
- A list of the devices your customers actually use, if you know it. We'll test on those first.
Need iPhone as well? See native iOS app development. Stores change their requirements every year, and keeping an app listed is ongoing work covered by mobile app support. Our experience with the UI toolkit: Jetpack Compose — two years in production.