Operational summary
The first phase is broader than Google Play. Google, HONOR, OPPO, Samsung, Transsion, vivo and Xiaomi stores participate in the initial regional deployment, so a Play-only audit can miss separately distributed builds.
Recommended sequence
- List each package by store rather than assuming one universal Android artifact.
- Record whether each store receives the same signing certificate or a channel-specific build.
- Check package registration for the identity users receive from every participating store.
- Track store-specific policy notices separately from the Android registration state.
Audit the channel, not only the brand
Android names Google, HONOR, OPPO, Samsung, Transsion, vivo and Xiaomi as participating organizations in the first phase. Availability and exact storefront presentation can vary by country and device, so use your distribution records as the inventory source.
The same package can be delivered through multiple stores with different signing processes. Capture the certificate on the actual channel artifact and keep store-specific policy work in a separate column.
- Confirm which listings are live in each affected country.
- Identify channel-specific APKs and signatures.
- Recheck after a signing or ownership migration.
Frequently asked questions
Is checking Google Play enough?
Not if the app is also available through another participating store or a separately signed channel.
Does PkgReady check store policy?
No. It checks official Android package registration status, not individual storefront approval.
Sources and review
PkgReady summarizes operational implications but does not replace an official console or Android documentation. Reviewed 2026-08-14.