Cado works or it doesn't on your phone, in your pocket, on your bike — combinations it can't meet any other way. That's what testing is: ride normally, and tell us when something surprises you.
Email cadoreports@gmail.com with the Google account address your phone uses for the Play Store.
You'll get an invite link back. Open it, accept, and install Cado from the Play Store like any other app.
That's it. New builds arrive through Play automatically. Then read the first ride guide — placement is the one thing worth getting right.
No scripts, no checklists. Ride as you normally would, and notice these:
In Cado: Settings → Report a bug or Request a feature. Either opens your own email app with a message ready to complete — app version, phone model and your current settings are filled in for you, visible and editable. Nothing is sent until you press send.
For anything about detection — wrong numbers, no lock, a number while coasting — attach the ride log: Summary → Share ride, and send the file wherever suits you. Or write to cadoreports@gmail.com directly; there is no wrong door.
A ride log is a plain file on your phone: every cadence reading, every state change, the battery curve. It holds no location, no name, no account — there's nothing of those to hold. It's yours; sharing one is always your choice, ride by ride.
When you share one, it becomes a permanent test case: every future build of the engine must get your ride right before it ships. A handful of riders sharing logs is how a two-person test programme gets the coverage of a big one.
They're also worth keeping for yourself. Hand a log to an AI assistant like Claude or ChatGPT and it can time-sync the ride with a Polar H10 or Strava recording — how your cadence moved with heart rate or gradient. The FAQ has the how.
Send them the front page — it makes the pitch in thirty seconds, no tester jargon. If they're keen, one email adds them. Riders you bring in count double: new phones and new pockets are the coverage we can't buy.