Conductor · build v74

Help us test

Conductor's whole premise is that your phone can call out timed cues from inside your pocket, screen off. Whether that survives depends on your exact phone and browser — which is why we need people who aren't us. Four tests, about ten minutes.

Open Conductorkeep this page open in another tab
Nothing leaves your phone unless you press Send. Results go to a public GitHub issue you review and submit yourself — no accounts here, no tracking, no background reporting. Prefer not to use GitHub? Copy the report instead.
T1The pocket test ~4 min

The one that matters most. Headphones optional; volume up either way.

  1. In the app, tap Try the Demo, then Start Practice.
  2. Lock your phone and put it in a pocket or bag.
  3. Leave it alone for two or three minutes. Don't peek — waking the screen changes the result.
Should hear Countdown beeps and cues continuing with the screen off. Tell us what you heard and roughly when — especially if sound stopped partway, or arrived late all at once.
T2Your own voice ~4 min

Recorded cues are the only spoken audio that survives a locked screen. Robot text-to-speech can't.

  1. Back on the app's first screen, tap Create New Event, give it a name, then add two actions.
  2. Tap 🎤 Record all cues. It asks for four things: each action, then its "Get ready to…".
  3. Tap ▶ Play all cues to hear them back, then run a practice with the phone locked.
Should hear Both halves in your own voice — "get ready to wave", then "wave" — with the screen off.
T3Could you work it out? ~1 min

Honest answers help more than polite ones. If something was confusing, that's a bug in our design, not in you.

  1. Anything you tapped that didn't do what you expected?
  2. Anything you went looking for and couldn't find?
T4Anything dead or weird as it happens
  1. Red bar across the top? Tap it — it copies the error. Paste it into the box below.
  2. Audio wrong? On the practice screen, tap the bordered audio: … ⧉ tap to copy box and paste that in.
Either way Tap, then paste. Those two things tell us more than any description could.

Anything else

Known limits — not bugs

The robot voice never plays with the screen locked; only recordings and beeps survive a pocket. Actions less than five seconds apart share one spoken heads-up. Moving the practice speed slider off 1× turns off pocket audio on purpose — the screen says so when it does.
Nothing marked yet