To publish a Glassly app on Google Play, create your own developer account, prepare a signed Android App Bundle, complete the store listing and required disclosures, and follow the testing and review steps in Play Console. Google charges $25 once for registration. A build is only one part of publication.
1. Register the publishing account
Follow Google's registration guide and choose the account type that matches the publisher. Identity and organisation checks vary by account type. With Glassly, the account is yours and you upload the release in your own Play Console. For client work, agree who will own that account before building.
2. Build and download the Android App Bundle
Glassly produces the signed Android App Bundle, or AAB, for store upload. The APK used for a direct phone install and the AAB submitted to Google Play serve different purposes. Keep the app identifier and signing arrangements consistent across releases, and follow the signing instructions in Play Console. Your own Supabase project is required for a production or store build.
3. Prepare the listing and disclosures
Add the name, descriptions, icon, screenshots and category. Complete the content-rating, target-audience, app-access and data-safety sections requested by Play Console. Check privacy information against what your app and its connected services collect. Any generated disclosure text needs your review after customisations and integrations.
4. Run the required test
Google's testing rules for new personal accounts apply to accounts created after 13 November 2023. They require at least 12 testers opted into a closed test continuously for 14 days before you can apply for production access. Direct APK installs do not satisfy this Play Console opt-in requirement. Recruit users, collect feedback and fix problems; reaching the minimum duration alone does not guarantee access.
5. Apply for production access and submit the release
Answer the questions about your test, feedback and readiness in Play Console. Google says the production-access review usually takes seven days or less but can take longer, and it may require further testing. Access approval and release review are separate steps. Set your launch date with room for both.
Do you need a public store listing?
Glassly also provides an Android install link and QR code for direct distribution. That avoids a public Play listing, but device permissions and Android developer verification still apply. See the installation guide for registration options and the regional verification rollout. Builds you hand to testers do not update themselves: testers install each newer build from the link. The copy on your own phone, and Android installs made for your team, pick up changes on their own.
What to include in the budget
Google's registration fee is separate from Glassly. Standard templates are free to create; changes use credits. Glassly does not add a separate build fee for producing the signed bundle. Include hosting in your own Supabase account and any external services your app uses. Our pricing page sets out plans, credits and external fees.
For a first project, follow the complete Glassly workflow and test a free template before committing to a public release.