Target API upgrades
Apps moved to the level Google Play now requires.
Mobile
Android app development that meets the Google Play rule
Since 31 August 2026 new apps and updates on Google Play must target Android 16. We have no published Android-native build, so we show the cross-platform apps nearby.
0Published Android-native builds
API 36Target for new apps and updates since 31 Aug 2026
API 35Existing apps need it to stay available to new users
1 Nov 2026Extension deadline Google offered
What we build
What we would take on for Android
Bluetooth LE apps
Permission model updated since Android 12, as for our pull-tester apps.
Background location
Foreground and background location requested separately since Android 11.
Android from one codebase
An Android app from a .NET MAUI or React Native project.
Architecture
Where an Android app would sit
An Android app in a field testing build
Devices
Pull testersBluetooth LE
Torque wrenchesBluetooth LE
App
Android appWhere it would sit
.NET MAUI appDigital Testing Platform
Back end
ASP.NET CoreWith Azure SQL
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Google Play
The 2026 target API rule
Google Play target API requirement
31 Aug 2026
Android 16 for new apps and updates
New apps and updates must target API 36. Wear OS and Automotive need API 35.
1 Nov 2026
Extension deadline
Developers could ask Google for more time, to this date.
Now
Check your target level
Existing apps on API 34 or lower reach only devices on the same or older Android.
Source: Android Developers, Target API level requirements for Google Play, checked 2 November 2026.
Builds
The closest builds we can show you
Statutory inspection, United Kingdom
Work-at-height anchor and torque platform
A .NET MAUI field app that reads pull testers and torque wrenches over Bluetooth LE, the work an Android app would do.
70%Faster reporting cycle
Dedicated team, Germany
Core development team
A React Native app for iOS and Android beside Node.js and .NET back ends.
60+Developers the team grew to
Fit check
When Android is the right call
Pick Android when
- Your users carry Android phones or rugged Android devices
- The app needs Bluetooth LE or background location
- Your app must clear the Google Play target rule
Look elsewhere when
- You need a published Android-native build to inspect, which we do not have
- You want one codebase for both stores, where we use .NET MAUI or React Native
- Your whole fleet uses iPhones, where our native iOS build applies
Explore
Same job, other tools
Where we used it
Stack
What Android usually ships with
Xamarin
React Native
Flutter
iOS
Node.js.NETFAQs
What buyers ask first
What does Google Play require in 2026?
From 31 August 2026 new apps and updates must target Android 16 (API 36). Wear OS and Automotive OS apps need Android 15, and Android TV and XR apps need Android 14. Existing apps need Android 15 to stay available to new users on newer Android.
Do you have a published Android-native build?
No. We say so on the first call and show the nearest work, which is a .NET MAUI app with Bluetooth LE and a React Native app.
How does Bluetooth work on newer Android?
Since Android 12 the old BLUETOOTH and BLUETOOTH_ADMIN permissions give way to BLUETOOTH_SCAN, BLUETOOTH_ADVERTISE and BLUETOOTH_CONNECT, and apps targeting Android 12 or later no longer need a location request for Bluetooth.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us which Android level you target
Thirty minutes on your app, your devices and the Google Play rule. No sales pitch.