Google tightens Play API control

Android app distribution is getting a new choke point — but it’s not quite the one the initial chatter makes it sound like. Google is not announcing a brand-new Play API tollbooth that suddenly hits everyone in September 2026. The real story is broader and, in some ways, bigger: Google is rolling out Android developer verification across both Play and non-Play distribution, and starting September 30, 2026, some users will hit extra friction when they try to install apps from developers Google hasn’t verified. ### So what actually changed? On March 30, 2026, Google said Android developer verification was rolling out to all developers in both Play Console and the newer Android Developer Console. That means the enrollment phase is live now. The user-facing enforcement comes later — first in Brazil, Indonesia, Singapore, and Thailand this September, then more broadly in 2027. ### Is this just a Google Play policy? No — that’s the key distinction. Google Play already had developer identity checks in place, and Google says most Play developers have likely already done what they need to do. The new layer extends the same logic to Android apps distributed outside Play, which is why sideloading communities and alternative stores are the ones sounding alarms. ### What does a developer have to do? There are two pieces. First, verify identity — legal name, address, email, phone number, and in some cases government ID. Organizations may also need a D-U-N-S number and website verification. Second, register package names by proving ownership of the app package signed with the developer’s key. ### What happens is the same unless they try to install an unregistered app. In those cases, on certified Android devices in the first four rollout countries, users will need ADB or an “advanced flow” to proceed. Basically, sideloading still exists, but it gets harder for normal people. ### Where did the “fees” part come from? There is a separate 2026 Google Play fee overhaul, and that may be getting mixed into this story. Google has published a new service-fee structure with lower rates in some cases and program-based discounts for developers that join new app and game programs. But that is not the same thing as Android developer verification, and the verification pages do not describe a new mandatory registration fee tied to the September 2026 enforcement date. ### Why are developers pushing back? Because this shifts Android closer to a permissioned system even outside the Play Store. F-Droid published an open letter in February calling the policy a breach of Android’s open model, and a broader coalition argued that forcing developers to register with Google threatens privacy, competition, and user freedom. That criticism is really about control — Google becomes through Play. ### Does Google have a defense here? Yes, and it’s straightforward. Google says sideloaded sources produce far more malware than Play, citing internal analysis showing over 90 times more malware from sideloaded sources than on Google Play. The company’s pitch is that identity checks deter repeat bad actors without fully killing sideloading, because power users can still use ADB or the advanced flow. ### What’s the bottom line? This is less “Google changed the Play API rules” and more “Google is extending Play-style identity control to Android itself.” For mainstream users, the change may barely register. For independent developers, alternative app stores, and open-source distribution, it could redraw the line between an open platform and one that stays open only if Google recognizes you first.