Guide summary
Evaluate Android's limited distribution account for teaching, hobby projects and very small device groups without government ID verification.
For: Students, teachers, hobby developers and private prototypes with a genuinely small user group.
Release sequence
- Confirm the expected device count will remain inside the official limit.
- Document who controls the authorized-device list.
- Avoid using the limited path for a public community that can outgrow the cap.
- Create a migration plan before moving to unrestricted distribution.
Quick facts
Treat the device limit as a product constraint, not a loophole for public distribution.
Detailed guidance
Treat the device cap as a product boundary
A limited distribution account is free and supports sharing registered apps with up to 20 explicitly authorized devices. The device authorization handshake is part of the distribution model, not a substitute for a public storefront.
Estimate the real audience before choosing this path. Classrooms, portfolios and family projects may fit; a growing beta community or customer deployment usually needs a full distribution plan.
- Document who authorizes and removes devices.
- Do not promise unlimited transfers between device lists.
- Plan a full-distribution migration before the audience outgrows the cap.
Have the production package name and signing certificate ready? Query the official registration state, then use the result to choose your next step.
Run status check →Frequently asked questions
Is government ID required?
Official guidance describes fewer verification requirements for the limited account path; check the current signup flow for the exact information requested.
Can it be used for a public app?
It is intended for small, controlled groups and caps sharing at 20 authorized devices, so it is not a general public-distribution model.
Sources and review
Last reviewed: