Skip to content
audiotale.net
Sign in
NewsNews

Android Registered App Stores open 1 December: $10,000 fee, Android 17 QPR2, not in the US

Google's optional program gives third-party app stores one-tap installs and background updates, in exchange for a fee, full catalogue scanning and a long list of rules.

audiotale.net team

· 7 min read

Written by AI from the sources linked below. How we use AI

On this page
  1. Key points
  2. What to do
  3. What happened
  4. Background
  5. How it works
  6. What it means
  7. What we don't know yet
  8. What to watch next
  9. Sources

Google has opened applications for Android Registered App Stores, an optional program that lets third-party app stores get one-tap installs and automatic background updates on Android, and it goes live on 1 December 2026. According to Google's developer documentation, stores must pay a $10,000 annual registration fee, hand Google their whole catalogue for malware scanning, and meet a list of security and policy requirements. The feature needs devices on Android 17 QPR2 or later, and it covers a list of regions that, per Google's FAQ, does not include the United States, the United Kingdom or most EU countries. For store operators it is a new gate to pass; for users in supported countries it could make installing from non-Google stores far smoother.

Key points

  • Registered App Stores become available on 1 December 2026 on devices running Android 17 QPR2 or higher, in the regions listed in Google's FAQ.
  • Registration is optional: a store that does not enrol keeps the standard sideloading experience, Google says.
  • The annual registration fee is $10,000, payable before Google starts its eligibility review, according to Google's enrolment guide.
  • Stores must upload their entire hosted catalogue and every new store APK for malware scanning, and must be a verified organisation in the Android Developer Console.
  • Variable extra fees apply if more than 1% of install attempts or 2% of apps in a store's catalogue over 30 days are found to be potentially harmful apps (PHAs), per Google's requirements page.

What to do

If you run an Android app store outside the US and Europe: read the requirements, then submit Google's interest form. Google validates your organisation account, developer and package-name verification, and brand legitimacy first, then sends enrolment instructions. Enrolment covers declaring policy URLs (privacy, trust and safety, developer agreement, illegal-content removal and others), uploading your store APK, and uploading the full catalogue. Then you pay the fee. You also need App Defense Alliance MASA (AL2) documentation, submitted in English, according to the enrolment page.

If you are a user: nothing changes on 1 December unless your device runs Android 17 QPR2 or later, your account's home country is on Google's list, and a store you use has registered. Stores that do not register keep working as before.

If you manage devices: Google's FAQ says IT administrators can block the installation of Registered App Stores on managed devices.

What happened

On 27 October 2026 Google published the program's documentation, and Ars Technica reported on it the same day. The overview page defines a Registered App Store as "a third-party app store that registers with Google to access additional platform capabilities, including one-tap installs", while upholding trust, security and performance standards. The program is optional.

What registration buys is mostly convenience, as the overview lays out. A standard sideloaded store needs the user to enable the REQUEST_INSTALL_PACKAGES permission manually, shows a confirmation dialog for every install, and needs approval for each update. A registered store gets that permission automatically once verified, installs apps in one tap with no extra confirmation screens, and updates in the background with user control settings.

Google's FAQ adds the practical details. Availability starts on 1 December 2026 on Android 17 QPR2 and higher, determined by the user's home account country; short trips abroad do not break installs or updates, and a permanent move updates the feature set. Large downloads must run as foreground services with visible notifications. If a user uninstalls a registered store, its apps stay but stop getting automatic updates from it, and reinstalling it restores update ownership without new prompts unless another store updated the apps in the meantime.

Background

Registered App Stores trace back to the antitrust fight over Google Play. Google's 4 March 2026 Android Developers Blog post, by Sameer Samat, described the program as optional and aimed at sideloaded stores that meet "certain quality and safety benchmarks". It said the program would begin outside the US and arrive in the US later, "subject to court approval", and launch with a major Android release by the end of the year.

Ars Technica adds that Google and Epic, after the trial, tried to settle in a way that gave Google more control, but withdrew the settlement when the court signalled it would not approve it. As a result, Ars says, Registered App Stores will launch without US support, and Americans looking for alternative stores will use Google Play, where Ars says Aptoide is so far the only one listed. We have not independently verified that last point. The 4 March post also described separate Play fee changes (a 5% billing rate in the EEA, UK and US, and a 20% service fee on in-app purchases for new installs, with a 10% fee on subscriptions); those are a different programme from the one covered here.

How it works

The program has five onboarding steps, according to Google's overview: submit the interest form; pass pre-qualification; pay the registration fee; apply and undergo technical evaluation; and, if approved, be activated as a Registered App Store. After activation the store's status is synced to the Android OS. To stay registered, every later version of the store APK must be submitted for malware screening, per the enrolment guide.

The requirements page sets the rules a store must keep:

  • Eligibility: a verified organisation in the Android Developer Console that has completed and maintains Android developer verification, with a registered package name. The store must be a standalone APK; web wrappers do not qualify.
  • Openness: the store must function as an open marketplace for all eligible developers with "clear, non-discriminatory policies", with direct contractual relationships and written authorisation from developers.
  • User experience: a dedicated launcher icon the user installs explicitly, uninstall from the same listing, no silent installs without consent, and no disruptive off-screen ads.
  • Security: proactive prevention of malware and PHAs; annual ADA Mobile Profile certification; MASA AL2 certification from 1 June 2027; integration with Google's catalogue submission API; fixing major vulnerabilities that are reported; no blocking other app stores or suppressing OS security notifications.
  • Later deadlines: a memory consumption limit policy by 1 December 2027, and a data safety section in listings from 1 December 2027.
  • Enforcement: non-compliance can lead to removal from the program, with advance notice and a chance to fix; stores primarily hosting content such as CSAM or terrorist material face immediate deregistration.

Google also states: "App stores remain responsible and liable for their entire catalog. Google won't moderate the content."

What it means

For store operators. The $10,000 yearly fee is small for a large store but significant for a hobby or community catalogue, and it is due before Google even reviews the application. Ars quotes Google as saying the fee covers additional support for running the program. The requirement to upload the whole catalogue and every new APK also hands Google ongoing visibility into a competitor's inventory, which is a trade-off each operator will weigh. Google's documentation says non-participating stores keep working as before.

For users. One-tap installs and background updates remove the main friction that sideloaded stores have today. Whether many stores register is not known yet.

For the device base. Ars points out that the program needs Android 17 QPR2, which it says is expected on Pixel phones in the coming weeks, and that devices in many supported regions often update slowly. In its view a substantial number of devices in supported countries may never receive a compatible update. That is Ars's assessment; Google has not published a device count.

What we don't know yet

  • Which stores will join, and how many; Google has published no list.
  • How many Android devices will be eligible at launch; no figures are published.
  • The full region list. Google's FAQ lists countries including Australia, Brazil, Canada, India, Indonesia, Japan, Mexico, Singapore, South Africa and South Korea, plus a "Rest of the World" entry, and does not state an exclusion list. We read the absence of the US, UK and most EU countries from that list; Ars reports the same.
  • How the program interacts with Android developer verification for sideloaded apps. The FAQ does not address it.
  • When, or whether, the US will be included, which depends on a court.

What to watch next

Watch for 1 December, when the first stores could appear as registered; for Android 17 QPR2's arrival on Pixel phones; for the first stores to announce they have paid the fee; and for updates to Google's FAQ, which says it will be revised as the program evolves. Also watch for any change in the US position as the court case develops.

Sources

SaveStart the discussion

Written by

audiotale.net team

The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.

Read next