Current Closed Test: 1.0.0 (1004)Recruiting target: 15 testersUpdated 18 August 2026
Current rule: Google Play's production-access threshold is at least 12 testers continuously opted in for the last 14 days. Feathly is recruiting 15 testers for a small buffer. Google does not set a fixed daily usage-time requirement; we recommend about 2–5 minutes of real use and useful feedback.
Start here · Test goal
Why does the Closed Test run for 14 days?
The goal is to verify Feathly in real Android environments, collect useful feedback, and build enough evidence of real testing before applying for Google Play production access.
Google's current threshold is at least 12 testers continuously opted in for the last 14 days before production-access application.
Feathly is recruiting 15 testers to keep a small buffer.
There is no fixed official daily usage-time requirement. About 2–5 minutes of natural use is normally enough for this test.
Please do not opt out of the Closed Test during the 14-day period.
Important: Google Group membership alone does not start the 14-day period. The continuous period starts after you complete Become a tester / Google Play opt-in.
Start here · Access and setup
Tester group → Google Play opt-in → install
Use the same Google account you submitted in the Feathly application form. Feathly registers that account in the Closed Testers group, so you do not need to join the Google Group manually.
Submit the Feathly Closed Test application and check the acknowledgement email.
Feathly adds the submitted Google account to Feathly Closed Testers. Google Groups may send you a member-added message.
If you see “App not available”: first check that the browser is signed in with the Google account you submitted. If group access or Play changes were only just applied, wait a little and retry. If it still fails, do not leave/rejoin the group yourself; contact Feathly Support.
Start here · Feedback
Use one Feedback Form for the whole test
Daily Check-in, Issue Report, Day 7 Midpoint Review, and Day 14 Final Review are all available in the same Google Form.
Daily Check-in: a very short note about that day's use.
Issue Report: send this whenever something breaks or behaves unexpectedly.
Day 7 Midpoint Review: summarize the first week.
Day 14 Final Review: summarize the overall test experience.
The form is written in English. If needed, use your browser's webpage translation feature. If translation is unavailable or unclear, you can continue in English.
14-day test plan · Days 1–4
Install, Recall, notifications, and editing
Start with the basic flow. A normal test day can take about 2–5 minutes.
Day
What to try
Record
Day 1
Complete Closed Test opt-in, install/update Feathly, first launch, allow notification permission if requested, and create one Spaced Loop.
Daily Check-in
Day 2
Open the Loop, complete one Recall, and check that the next Recall timing looks natural.
Daily Check-in
Day 3
Prepare a near-term Recall, send Feathly to the background, then check that the notification arrives and opens the app correctly.
Daily Check-in
Day 4
Edit a Loop title/settings, delete one test Loop, and confirm the screens refresh immediately and remain correct after reopening.
Daily Check-in
14-day test plan · Days 5–7
Recall Now, Focus Timer, and midpoint review
Day
What to try
Record
Day 5
Use Recall Now and confirm Home updates immediately, especially the NOW/current-task grouping.
Daily Check-in
Day 6
Start Focus Timer, move to the background, check notification/state, return to the app, then Pause or End.
Daily Check-in
Day 7
Review one week of use and Weekly Insights. Note the best part, the most confusing part, and anything you would change.
Day 7 Midpoint Review + Daily Check-in
14-day test plan · Days 8–10
Routine Loops, several Loops, and persistence
Day
What to try
Record
Day 8
Create and complete a Routine Loop. Check how Routine and Spaced Loops appear together on Home.
Daily Check-in
Day 9
Use several Loops and complete several Recalls in a row. Watch for stale Home/Loops states, duplication, or confusing navigation.
Daily Check-in
Day 10
Fully close and reopen Feathly, move between background and foreground, and confirm created data and completion states are preserved.
Daily Check-in
14-day test plan · Days 11–14
Readability, backup, optional PRO, and final review
Day
What to try
Record
Day 11
Check Settings, dark mode/display readability, clipped text, overlapping controls, small tap targets, and unclear wording.
Daily Check-in
Day 12
Create a backup. If you are comfortable using test data, also try Restore and confirm the expected data returns.
Daily Check-in
Day 13
Only if Google Play clearly shows a test payment method, try the PRO purchase flow. Otherwise skip billing and continue normal Loop/Recall testing.
Daily Check-in
Day 14
Use the core features freely, check any remaining issues, and evaluate the whole 14-day experience.
Day 14 Final Review + Daily Check-in
Core feature checks · Loop / Recall
Loop and Recall
Check the flow from creation through Recall completion and the next generated step.
Spaced and Routine Loops create normally.
Saved Loops appear immediately on Home/Loops.
Data remains after reopening the app.
The next Recall follows naturally after completing one.
Completed Recalls do not duplicate or remain incorrectly in NOW.
Home refreshes immediately after Recall Now.
Core feature checks · Notifications
Notifications
A reminder arrives around its scheduled time.
Notifications can arrive while Feathly is in the background.
Tapping a notification opens Feathly correctly.
The same notification does not repeat unexpectedly.
Android note: Force stop can block scheduled work. Swiping an app away from Recent Apps is not the same as Force stop.
Feathly uses the Closed Test group for license testing as well. Only run a purchase test when Google Play clearly shows a test purchase notice and a test payment method.
If no test payment method is shown, do not purchase. A test-track user who is not recognized as a license tester can be charged using a real payment method.
If the device has several Google accounts, check the account shown in the purchase dialog.
The account that downloaded the app is normally used for the purchase.
Never send card details or payment credentials to Feathly.
PRO / purchase testing · Lifetime PRO
PRO test cases
Open the PRO purchase screen while in FREE state.
If Test instrument, always approves is available, complete a successful purchase and confirm PRO activates immediately.
Close and reopen the app and confirm PRO remains active.
If practical, use always declines and confirm a failed purchase does not activate PRO.
If practical, test a delayed payment method and verify pending → purchased / canceled behavior.
Lifetime PRO is non-consumable, so a valid purchase should not require buying the same entitlement again on the same account.
Optional: Skip billing if you are uncomfortable with it or no test instrument is shown. When reporting a billing issue, include the purchase account, test instrument, and the PRO state shown by the app.
Feedback and finish · Daily Check-in
Keep the Daily Check-in short
About 20–30 seconds is enough. Tell us whether you used Feathly, what you tried, and whether anything felt wrong.
If the app provides Copy Support Info, pasting that diagnostic context can help. Do not include passwords, payment details, or sensitive personal notes.
Feedback and finish · Midpoint / final review
Day 7 and Day 14 reviews
Day 7: tell us what feels useful, what is frustrating, what you would keep using, and what was confusing.
Day 14: summarize the overall experience, the most useful features, remaining issues, and whether you would use Feathly after launch.