Android developer verification, the API 36 deadline and Googlebook

Android now requires verified developers in four countries, Google Play has required API 36 since August 31, and Googlebook runs Play apps on laptops.

AndroidGoogle PlayGooglebookAdaptive UI

Google changed how Android apps reach users on three fronts between August 18 and September 30, 2026. Developer verification went live in four countries on September 30, Google Play started requiring Android 16 (API 36) for new apps and updates on August 31, and Googlebook laptops opened for pre-order on September 21. If you ship Android apps with Flutter, React Native or native code, each of these comes with a deadline or a new device class.

What changed

Developer verification is live in four countries

Since September 30, 2026, apps must come from verified developers to be installed from participating stores in Brazil, Indonesia, Singapore and Thailand. The rule applies on certified devices running Android 7 or later. The participating stores are Google Play, HONOR App Market, OPPO App Market, Samsung Galaxy Store, Palm Store, V-Appstore and GetApps. Google plans to expand verification globally in 2027 and beyond.

Google Play registers 99% of apps automatically. Developers use Play Console to register the rest, along with any apps they distribute outside Play. Developers who do not use Play at all register through the new Android Developer Console. For students and hobbyists, limited distribution accounts allow sharing an app with up to 20 devices without a government ID or a registration fee.

Unregistered apps can still be sideloaded

Google's announcement is explicit: "Unregistered apps can be sideloaded with Android Debug Bridge (adb) or advanced flow." According to 9to5Google, the advanced flow began a gradual rollout on August 18, 2026, and it includes a mandatory 24-hour wait.

API 36 is the new Play target

From August 31, 2026, new apps and app updates on Google Play must target Android 16 (API 36). Existing apps must target API 35 to stay visible to new users on newer devices. Developers who need more time can request an extension to November 1, 2026.

Other form factors have lower floors. Wear OS and Android Automotive apps need API 35, while Android TV and Android XR apps need API 34.

Googlebook brings Play apps to laptops

Googlebook is an Android-based laptop line from Acer, ASUS, Dell, HP and Lenovo. Pre-orders opened on September 21, 2026, prices start at $899, and the laptops reach US shelves on October 4. They run Play Store apps alongside desktop Chrome.

On September 22, Google asked developers to support window size classes, keyboard and trackpad input, multi-instance and drag-and-drop on Googlebook. Apps optimized for it get badging and featured placement on Play.

What it means for your app

Every APK needs an owner

If you publish only on Google Play, there is a good chance your apps are among the 99% registered automatically. Check anyway, since a missed registration blocks installs. The bigger exposure is everything you ship outside Play: internal tools, APKs sent to beta testers and builds on regional stores. Each needs a registered identity and package name, or installs will be blocked in the four launch countries now and, once verification expands, worldwide.

For agencies and freelancers, this raises a practical question: whose identity registers a client's package names. Settle that before the global rollout, while there is no deadline pressure.

Sideloading for QA still works, with friction

Developers and QA teams can keep installing unregistered builds with adb. End users on the advanced flow face a 24-hour wait, which rules it out as a channel for anything time-sensitive, such as a hotfix sent directly to a customer.

targetSdk 36 brings behavior changes

Raising targetSdk to 36 brings Android 16 behavior changes to your app, and that applies to Flutter and React Native apps as much as native ones. If you missed August 31 without an extension, updates are blocked until you comply. With an extension, the same block applies from November 1. Keeping existing apps at API 35 or higher matters too, since falling below it hides them from new users on newer devices.

Googlebook rewards adaptive layouts

On Googlebook, a phone app becomes a laptop app with a keyboard, a trackpad and windows of many sizes. The features Google lists match what laptop users will try first. Badging and featured placement give you a concrete reason to do the work, and adaptive layouts now pay off on both platforms, since Apple's foldable iPhone Duo needs them as well.

A practical checklist

Open Play Console and confirm that every app you publish is registered for developer verification. Register any that are not.
Inventory every APK you distribute outside Play, including internal tools, tester builds and regional store releases. Register the identity and package names through Play Console or the Android Developer Console.
If you have users in Brazil, Indonesia, Singapore or Thailand, test a fresh install on a certified device from each participating store you use.
Document the adb sideloading path for QA so testers are not blocked by unregistered builds.
Ship new releases with targetSdk 36. If you requested an extension, put November 1 on the calendar with a buffer.
Run your regression suite on Android 16 with the new target, and check Wear OS, Android Automotive, Android TV and Android XR apps against their own floors.
Test your app in large and resized windows with keyboard, trackpad, multi-instance and drag-and-drop, using window size classes to drive layout.

My take

Verification is the change with the longest tail. Four countries today is a soft launch, and the stated plan is global expansion from 2027. Every team that hands out APKs outside Play should make registration part of the release process now, while mistakes only affect a few markets.

The API 36 requirement is the yearly target bump, and most teams will absorb it with a regression pass. The risk sits in apps that rarely ship updates, where the target falls behind quietly and the deadline arrives before anyone has looked at the build.

Googlebook is the opportunity in this list. I would not rebuild an app for a laptop line that only reached US shelves on October 4. The work Google asks for is the same adaptive work iPhone Duo needs, though, so one investment serves two new device classes.