How we score
Every app is run through the same 100-point rubric on the same protocol. We open the app, time the setup, count the taps, cancel the trial, and publish what happened.
The rubric
| Criterion | Weight | What it measures |
|---|---|---|
| Setup friction | 20 | Minutes and decisions from install to first real value |
| Capture friction | 15 | Taps to Capture, measured with the published protocol |
| Forgiveness | 15 | What happens after a missed day: repair options, no shame loops |
| Reward design | 10 | Motivating without manipulating: no fake urgency, no loss-framed pushes |
| Notification quality | 10 | Helpful re-engagement vs noise; snooze and quiet controls |
| Price honesty | 10 | Trial terms as written vs as experienced; we cancel every trial |
| Accessibility | 10 | Text scaling, screen reader labels, reduced motion, contrast |
| Staying power | 10 | Update cadence over 12 months, team and funding signals |
The tap-counting protocol
Taps to capture is counted from a locked phone to a saved task with a due date, on a stock device with no widgets pre-placed. We repeat the run three times and publish the median. If a shortcut exists but requires setup, we count the setup separately under setup friction.
Verdicts
- KEEP — it survived a full test cycle and we would leave it installed.
- TRIAL FIRST — promising, but the fit depends on something specific about you.
- SKIP — the friction, price, or design cost outweighs the help.
Confidence levels
Hands-on means we installed and ran the protocol. Partial means some criteria could not be tested (paywalled tiers, waitlists). Community means the entry is summarised from documented user reports and is never scored as if we had tested it.
Corrections
Found a wrong fact? Email corrections@bestadhdapps.com. Corrections get a dated changelog line on the page they affect. Read the editorial policy.