Help prove the return loop on real Android devices.

Why a closed test is required

New personal Google Play developer accounts must complete Google’s required closed-testing period before applying for production access. CueMeThen plans to recruit 15–20 testers so at least 12 remain continuously opted in for 14 days.

What testers will exercise

• Anonymous offline capture, editing, Boards, Today, Inbox, search, backup, restore, and recovery.
• Local reminders, notification permission, exact-alarm access, reboot, time-zone changes, and missed delivery.
• Text, link, photo, voice, Android sharing, interrupted capture, process death, and low-storage behavior.
• Email/Google sign-in isolation, Play Integrity, optional cloud adoption, multi-device conflicts, and export/deletion.
• Google Play license purchases, restore, upgrade, downgrade, expiry, and refund behavior where tester eligibility permits.
• Optional AI consent, allowance, provider failure, and suggestion review.

Privacy for testers

Do not send note content in feedback. Use synthetic notes for provider, AI, or purchase tests. Feedback should include device model, Android version, app version, steps, expected result, actual result, and approximate time. Sanitized screenshots must not show private notes, emails, purchase evidence, or tokens.

Read the privacy notice before opting in.

What participation means

Closed-test software may contain defects and may receive updates with higher version codes. Testers can leave the test at any time, but leaving may reset the continuous tester count required for production access. Participation does not guarantee free paid subscriptions, compensation, or continued access.

Production remains gated

CueMeThen will not request production access until the required testing period completes and critical security, privacy, backup, provider, purchase, deletion, accessibility, performance, and physical-device checks pass.