Guide summary
Prepare package names and signing certificates for apps distributed through websites, open-source channels or third-party stores.
For: Open-source projects, enterprise distributors and independent app stores.
Release sequence
- Inventory packages distributed outside Play and identify their maintainers.
- Choose the appropriate full or limited distribution account path.
- Prove package ownership using the current signing identity and console workflow.
- Recheck each package and certificate pair after registration.
Quick facts
Registration is not permission to publish in a particular third-party store. Each store can retain its own submission and policy requirements.
Detailed guidance
Choose the correct console path
Developers distributing only outside Google Play use Android Developer Console to verify an individual or organization and register package names. The console can require a package name, certificate fingerprint and signed APK ownership proof for an existing package.
Keep store approval separate from Android registration. An alternative store can still require its own identity, content and artifact checks after the package is registered.
- Full distribution accounts support broad distribution.
- Limited distribution is designed for small authorized device groups.
- ADB and the advanced flow are distinct installation paths.
Frequently asked questions
Can a Play developer register an outside-Play app?
Official guidance says Play developers can also register outside-Play packages through available Play Console workflows.
Does registration publish my app?
No. Registration links identity, package and signing information; publishing remains a separate store or distribution action.
Sources and review
Last reviewed: