Google Play Closed Testing

Google has asked me to run another 14-day closed test before I can move the app into production. My goal this time is simple: prove overall stability. I need real testers who will install the current internal-testing build, use the app as they normally would, and share any crashes, UI glitches, or performance slow-downs they encounter.

Here is how I picture the flow:
• I provide the Play Console invitation and the latest build (already uploaded as a closed-test track).
• Over the next two weeks you actively engage with the app—opening it multiple times a day, navigating every screen, and exercising as many features as possible.
• Whenever something feels off, you send a concise report (device model, Android version, steps to reproduce, screenshot or logcat if available).
• Mid-test I push one or two incremental APK updates based on your feedback, and you confirm the fixes.

Acceptance criteria
• Minimum two weeks of continuous usage by at least a handful of unique devices.
• No unhandled crashes reported in Play Console by the end of the period.
• A brief summary document outlining issues found, fixes verified, and any remaining concerns.

If you have prior experience testing Android apps through Google Play’s closed tracks and can commit to active daily usage, I’d love to get started right away.