Android apps tested on the phones your users carry
Hashlogics is an Android app development company that builds in Kotlin or React Native and tests on the low-end phones your users carry. We keep each app current with Google Play's rules after launch, and the first 2 months of maintenance come with every build.
- 4.8 on Clutch across 22 reviews
- PremiumAudit.io: audit cycle cut 75%, calculation errors cut 95%
- In production for SmartREI, Tankaware, ZyloBase, KiwiWrite
Android isn't one phone. Your app will run on handsets with different screens, Android versions and amounts of memory. When memory runs low, Android kills processes in the cache, and it can end the ones holding the most memory. If your app hasn't saved its state, a half-filled form is gone when the user comes back. So we settle the test plan before we write the first screen. What's the oldest Android version you'll support? Which phone in the set has the least memory, and what does your app do with no signal?
Google Play's numbers
The numbers Google Play holds your Android app to
1.09%
user-perceived crash rate: Google Play's overall bad behavior threshold
API 36
the Android 16 target new apps and app updates need since 31 August 2026
12 testers
in a closed test for at least 14 days, for personal Play accounts created after 13 November 2023
Android work we take on
The kinds of app we build, with the systems behind them where we have them. Your Blueprint records the Kotlin or React Native choice, and the reason, before the build starts.
Kotlin apps that use the whole phone
We write native Android apps in Kotlin when the app lives on the hardware: background location, Bluetooth devices, the camera or long-running sync. Google announced at I/O 2019 that Android development would be increasingly Kotlin-first. It now recommends starting new Android apps in Kotlin.
React Native apps for Android and iPhone
When your app is screens, forms and data that iPhone users need too, one React Native codebase can serve Google Play and the App Store. It isn't a web page in a wrapper: at runtime, React Native creates the corresponding Android views. A new Android feature may need some native code first. BrandLocator, a bilingual store discovery app we built with Expo and React Native, is live on Google Play.
Native vs React Native, compared →
React Native field and staff apps
TankAware runs petroleum tank and site inspections across five roles, from Super Admin to Contractor, with a React Native mobile side. Shift Link checks a UK agency worker's right to work before a shift is scheduled, on the web and in its React Native app. Both case studies are below.
- ScopeFree scoping call, then a fixed-fee Blueprint, credited in full.
- ChooseKotlin or React Native, in writing.
- Set devicesLowest-memory phone and oldest Android agreed.
- BuildSaved state and offline first, screens after.
- Closed testYour testers on a Play testing track.
- ReleaseFrom your own Play Console account.
Seven stations, and the device set comes before the build. Choosing test phones after the app exists means finding the memory problems last.
Low-memory phones and no signal
Android (Go edition) is Google's version of Android for entry-level smartphones with less RAM than higher-end devices. Your app may run on one of those, or on a mid-range phone with little memory to spare. Either way, Android can end your app's process while it waits in the background.
Google Play's Android vitals put a number on it. The bad behavior threshold for user-perceived crash rate is 1.09% across devices, and 8% on a single phone model. So a crash that only hits one cheap model can count against you while your average looks fine. If your app goes over a threshold, Play may reduce its visibility and may show users a warning on your store listing.
Memory is now a store question too. Google lists memory usage as a core vital for all mobile apps, with thresholds for each device RAM tier. It says apps over those thresholds may see store visibility impact starting from February 2027.
So we design for both from the start. Work that must finish, like an inspection upload, goes to WorkManager. That's the Jetpack library Google recommends for tasks that keep running after the app leaves the screen. Its tasks persist across app restarts and device reboots.
- A low-memory phone sits in the test set from the first build, next to the newest one.
- Forms save as the user types, so a killed process doesn't cost anyone their work.
- Uploads wait for a connection and retry, and the user can see what is still queued.
- Images are sized for the screen, because bitmap memory usage is a core vital of its own.
The rules Google Play sets for your Android app
Since 31 August 2026, new apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play. Wear OS, Android Automotive, TV and XR apps have lower targets. Existing apps must target Android 15 (API level 35) or higher to stay available to new users on phones running a newer Android version.
Every developer with an app published on Google Play must complete the Data safety form, even if the app collects no user data. It must also reflect data that third-party code, such as SDKs, collects or shares. We list each SDK in your app, and what it sends, before anyone fills the form in.
Does your app let users create an account? Then Google Play requires an in-app path to delete that account and its data, plus a web link for deletion requests. Google allows an app to retain certain data for legitimate reasons such as security, fraud prevention or regulatory compliance. In that case, you must clearly tell users about your retention practices.
New personal developer accounts have one more step. If your personal account was created after 13 November 2023, you must run a closed test before you can apply for production access. It needs at least 12 testers, opted in continuously for at least 14 days. We plan that test inside the build. Each release is built to these rules, and Google makes its own review decisions.
What we build Android apps on
Mobile
- Kotlin
- React Native
- Expo
- TypeScript
- or your existing Android codebase
Backend
- Supabase
- PostgreSQL
- FastAPI
- Node.js
- Laravel
- or the backend you run
Release and run
- Google Play Console
- Expo EAS
- Sentry
- GitHub Actions CI
- SonarQube
- or the CI and monitoring you run
Shipped integrations
- Mapbox
- UK Right to Work API
- IoT tank sensors
- or your own APIs
Tell us which phones your users carry
A senior engineer reads every brief. Work starts with a free scoping call, then a fixed-fee Blueprint, credited in full against the build. If the plan isn't one you'd act on, you don't pay for it.
“TankAware has revolutionized how we manage petroleum sites. The real-time data and automation have exceeded expectations.”
Blake Sutherland · President, Sutherland Excavating Ltd.
What to get in writing from any Android company
Good Android firms answer these questions in detail. Ask for the answers in writing, whoever you hire.
Test phones
What a clear answer names
Named phone models and the oldest Android version the app will support.
How we answer it
Agreed in the Blueprint, with your lowest-memory phone in the set from the first build.
Target API level
What a clear answer names
Who updates the app when Google Play raises its target, and by when.
How we answer it
Covered by the service level or your trained handover. Your first 2 months of maintenance are included.
Data safety form
What a clear answer names
Who lists each SDK and what it collects or shares.
How we answer it
We list every SDK and its data before the form is filled, and update the form when an SDK changes.
Play account and code
What a clear answer names
Whose name is on the Play Console account, and who owns the code.
How we answer it
Yours. We publish under your account, and you own the source code, the data and all intellectual property from day one.
Crashes after launch
What a clear answer names
Which tool reports them, who watches it, and how fast they respond.
How we answer it
Crash reporting we watch, against response times written into the service level.
01What does an Android app development company do?+
An Android app development company plans, builds, tests and releases Android apps through Google Play, then keeps them current as Android and Play's rules change. Hashlogics builds in Kotlin or React Native, tests on the low-end phones your users carry, and stays on the app after launch.
02Should we build our Android app in Kotlin or React Native?+
Build in Kotlin when your app depends on hardware or background work. Use React Native when it's screens and data that iPhone users need too. Google recommends starting new Android apps in Kotlin. We built BrandLocator in React Native with Expo, and its Android app is live on Google Play. Your Blueprint records the choice and the reason.
03Which Android phones will you test on?+
We test on a device set we agree with you, built from the phones your users carry. It includes the oldest Android version you support and at least one low-memory phone. Google Play sets a crash-rate threshold for each phone model as well as overall, so one weak model matters.
04Can you guarantee Google Play approval?+
No firm can promise approval, because Google makes its own review decisions. We build each release to Google Play's policies. That means the current target API level, an accurate Data safety form, and account deletion where your app has accounts. When Play flags something, we fix it and resubmit.
05What is Google Play's closed testing requirement?+
Personal developer accounts created after 13 November 2023 must run a closed test before applying for production access. It needs at least 12 testers, opted in continuously for at least 14 days. We plan that test inside the build and invite your testers early. Check which kind of Play account you have before you set a launch date.
06Will our Android app work offline?+
Yes, when offline is designed in from the start. On a low-memory phone, Android can end your app's process while it waits in the background. So forms save as the user types, and uploads wait for signal and retry. Work that has to finish goes to WorkManager, whose tasks persist across app restarts and device reboots.
07What happens when Google raises the target API level?+
Your app gets moved to the new target and retested, under a service level or by your own team after a trained handover. Since 31 August 2026, new apps and app updates must target Android 16 (API level 36). Every build includes the first 2 months of maintenance.
08Can you take over an Android app another team built?+
Yes. We read the code, run the app on your device set, and check its target API level, vitals and Data safety answers. Then we report what to fix and what to replace. After a free scoping call, that review is the fixed-fee Blueprint, credited in full against the build. If the plan isn't one you'd act on, you don't pay for it.
09How much does Android app development cost?+
There's no honest range before an engineer reads your systems. Cost moves with the platforms you need, how much of the app must work offline, and how many systems it talks to. Your scoping call is free. After it, a fixed-fee Blueprint, credited in full against the build, fixes the price for each milestone.
10Do we own the app and the Google Play account?+
Yes. We publish under your own Google Play developer account, and you own the source code, the data and all intellectual property from day one. The Play listing is already in your account. We hand the upload key and build credentials to you in writing, so your own team can ship the next release.
11Is this for enterprises or startups?+
Both, and on Android the Play account shapes the launch. Google asks a business to use an organization account, which needs a D-U-N-S number. A personal account created after 13 November 2023 must also run a closed test with at least 12 testers for 14 days. For an app with a large user base, a staged rollout sends each update to a percentage of users first. Managed publishing lets you choose when approved changes go live.
Related
- Mobile app development →iOS and Android apps, built and kept working.
- Native vs React Native →When one codebase is enough, and when it isn't.
- React Native vs Flutter →The two main cross-platform options, side by side.
- Hire React Native developers →Add a React Native engineer to your own team.
- Software maintenance →What keeping an app running after launch covers.
- How much does it cost to build an app? →What moves the number before anyone quotes.
- BrandLocator case study →A map-first app on Google Play, with its admin portal.
