Google opens enrollment for Registered App Stores: one-tap installs and silent updates outside the US from December 1, at $10,000 a year

On October 27, 2026, Google opened enrollment for its Registered App Stores program: a scheme in which third-party Android app stores register with Google and, once approved, gain the two capabilities that until now only the Play Store had — installs without the system’s secondary confirmation dialog, and silent background updates. Per the official documentation, the program goes live on December 1, 2026, on devices running Android 17 QPR2 and higher, outside the United States. Entry is not free: Google charges a fixed annual fee — reported by Ars Technica at $10,000 — and approved stores must continuously share their complete app catalogs with Google for malware scanning.

Key points

• Enrollment runs in five steps per Google’s overview page: interest form, pre-qualification, payment of a fixed annual fee, technical review (store APK plus full catalog for malware scanning), activation. Google’s pages say only “fixed annual registration fee”; the $10,000 figure and the pay-before-review order come from Ars Technica’s reporting.
• Coverage: from December 1, 2026, on Android 17 QPR2+ devices in 100-plus regions listed in Google’s FAQ — Canada, Australia, Japan, South Korea, India, Brazil, Hong Kong and Taiwan among them. The US is not on the list, and neither are major European markets like Germany, France or the UK.
• Staying in costs more than getting in: catalogs where Potentially Harmful Applications exceed 1% of install attempts or 2% of listed apps over 30 days trigger variable fees, and App Defense Alliance MASA AL2 certification becomes mandatory on June 1, 2027.

Background

The program has been on the calendar since March. On March 4, 2026, Sameer Samat, President of the Android Ecosystem, announced it in a blog post titled “A new era for choice and openness,” writing that it would “begin outside of the US first, and we intend to bring it to the US as well, subject to court approval.” That qualifier is the Epic v. Google antitrust judgment talking: Judge James Donato’s injunction orders Google to carry third-party stores inside Play for US users. According to Ars Technica, the Registered App Stores program was originally part of a Google–Epic settlement that was withdrawn after the court signaled it would not approve it.

Seven-plus months later, the international half has shipped on schedule, while the US took a different route: under the court order, US users can already reach third-party stores inside the Play Store, and Ars Technica notes Aptoide is so far the only one listed there. We have covered other cracks in the distribution wall — Google Play hosting personal vibe-coded apps earlier this month, and Australia’s court order forcing Apple to open iOS last week. Both mobile walled gardens are being taken apart, jurisdiction by jurisdiction.

How enrollment works

Google’s enrollment documentation splits the process into five steps. First, the interest form: organization identity details, public distribution links, and the Google Account tied to the Android Developer Console. Second, pre-qualification — Google checks the organization account, developer and package-name verification status, and brand legitimacy, then invites approved candidates to apply formally in the console. Third, payment of the annual fee. Note the order: the money is due before the technical review, which Ars Technica pegs at $10,000 per year. Fourth, the technical evaluation: submit the store APK for malware scanning, declare the required policy URLs, and integrate with the catalog submission API so Google continuously receives the complete app catalog and all subsequent updates for security review. Fifth, activation — the store’s status flips to Registered App Store and the new capabilities switch on.

The requirements page sets the technical bar concretely: the store APK must target an SDK level at most one major version behind the device (N-1), declare the INSTALL_PACKAGES_AS_REGISTERED_APP_STORE and REQUEST_INSTALL_PACKAGES permissions, and handle the intents app stores are required to support. Stores that sit out keep, in Google’s words, “the same experience as any sideloaded app” — per-install confirmations and manual updates included.

The obligations

The annual fee is just the cover charge. The requirements page lists ongoing duties that compound: a store stays responsible and liable for its entire catalog, and Google explicitly will not moderate registered stores’ content; if Potentially Harmful Applications exceed 1% of install attempts or 2% of catalog apps within a 30-day window, Google assesses variable fees to screen and remediate the high-risk catalog; stores must achieve and annually renew App Defense Alliance Mobile Profile certification (MASA AL2, mandatory from June 1, 2027); app listing pages need a data safety section by December 1, 2027, the same date a memory-consumption policy becomes required. Stores whose primary purpose is hosting CSAM, NCII, terrorist content or systemic financial fraud face immediate deregistration; unpaid invoices sit a tier lower, with possible suspension from the program until the issues are resolved.

For teams running stores or distribution channels outside the US, the arithmetic has a five-week deadline. Enrolling buys Play-grade install UX and automatic updates, at the price of the fee, full catalog visibility for Google, kept security liability, and exposure to threshold fines. Declining leaves sideload friction in every supported region — and friction at the “unknown sources” dialog is where conversion goes to die. Ars Technica flags a third constraint: many devices in supported countries may not receive Android 17 QPR2 for years, shrinking the audience the benefits apply to.

What others say

Google’s spokesperson gave both outlets the same line: the program offers third-party app stores “a more streamlined way to reach users while maintaining the safety and security of the Android ecosystem,” with eligible stores outside the US able to apply ahead of the simplified install experience arriving later this year. Ars Technica’s Ryan Whitwam focused on cost and friction: the fee-before-review order, English-only documentation, uploading copies of every app, and a rollout that skips the US and Europe while many local devices can’t run the required OS build. Android Authority’s Ryan McNeal added the feature comparison: approved stores get early access to new tools including the Android Developer ID API, and non-enrolled stores keep their current flow unchanged. The piece ends with a reader poll in which 92% of 549 voters expect Google to tighten sideloading in the future.

Our take

For users in supported regions this is a straight upgrade: installing a third-party store stops meaning tapping through “install anyway” warnings, and apps update themselves again. The decision that actually needs making, though, belongs to store operators, and the window closes December 1. The structural move deserves more attention than the UX: Google did not open sideloading — it turned convenience into a registration scheme, where the annual fee, the full catalog share, the PHA penalties and the MASA certification each act as a filter. That 92% poll comes from one site’s readership, so read it as a mood, and “convenience for control” still rhymes with what Apple is doing under the EU’s DMA — except this time enrollment is voluntary. The first signal worth watching after December 1: which stores besides Aptoide consider the $10,000 well spent.