Operational summary
Brazil is one of the four initial enforcement countries. Teams should map packages to participating stores and verify production signing identities before the milestone.
Recommended sequence
- Segment install and update volume for Brazil by store.
- Check every production package and signing certificate pair.
- Prepare Portuguese user support copy for registration-related install friction.
- Monitor official store and Android notices through the rollout.
Brazil release-room checklist
Use Brazil storefront availability and update traffic to decide exposure. Create one row for every Google Play or participating OEM-store listing available to Brazilian users, then attach the actual package and delivered certificate.
Prepare Portuguese support language that distinguishes registration-related installation friction from unrelated device compatibility or store-policy issues. Monitor rollout evidence by store instead of assuming every Android install behaves identically on day one.
- Owner for every unresolved package.
- Portuguese support escalation path.
- Post-rollout checks across representative certified devices.
Frequently asked questions
Does a company need to be based in Brazil?
No. Exposure is based on distribution to users in Brazil, not the developer's headquarters.
Are direct website APKs part of the first store list?
The first milestone is scoped to named participating stores; use current Android guidance for sideloading and later global expansion.
Sources and review
PkgReady summarizes operational implications but does not replace an official console or Android documentation. Reviewed 2026-08-14.