Help from Anywhere

You don't have to be in the room to help build this.

Conductor is a free, private tool that lets a group of people coordinate in real time using nothing but their phones — everyone's phone plays the same timed cues at the same moment, so a crowd can freeze, wave, light up, or move together on a shared beat. No app store, no accounts, no server. If you've never seen it, open the demo first: https://quidam2k.github.io/conductor/index.html?demo

We record voice cues and write event scripts together in person every couple of weeks. But a lot of the most useful work doesn't need a meeting — you can do it on your own time, from anywhere, and send it in. This page is that work.

Generated November 11, 2026. This page updates on a regular cadence — check back for the current ask.

What we could use right now

Pick one of these. Any single one genuinely helps — you don't need to do both.

• iPhone on iOS 26: do the beeps, voice cues and the new robot voice keep playing with the screen locked? — We've confirmed beeps and recorded voice cues on iOS 18 with the phone locked in a pocket, but not yet on iOS 26. New in build v73: typed cues are read by a built-in robot voice that goes into the same locked-screen track, and nobody has tried it on a locked iPhone yet. On an iPhone running iOS 26, open the Help Us Test page (https://quidam2k.github.io/conductor/test/) and follow the steps; then also open the app, paste a two-line typed event (for example 0:30 Freeze and 1:00 Unfreeze), tap Practice, lock the phone for 3 minutes and listen. Tip: in Safari tap Share → Add to Home Screen and open Conductor from that icon (Safari's new bottom toolbar can cover the Go Live button). Tell us in a GitHub issue: your iOS version, the build number at the bottom of the home screen, whether the beeps, voice cues and robot voice played with the screen locked, and whether they were on time.
• Two phones on hand? Time a voice-pack beam — Conductor can send a voice pack from one phone to another with no internet, as an animated QR code. Our first real test took about 3 minutes, and we want it faster. On phone A: open the app, tap Try the Demo → Install voices, then Manage Packs → Beam on that pack. On phone B: open the app → Scan QR Code → aim at phone A. If it stalls, tap "Trouble scanning? Smaller frames" on phone A or lower the speed. Report both phone models, the seconds it took, and the speed and frame settings that worked.
• Five minutes with your phone: does it work in your pocket? — Open the Help Us Test page (https://quidam2k.github.io/conductor/test/) on your phone and follow the steps. It checks whether Conductor's audio keeps playing with the screen locked on YOUR device. Nothing is sent unless you choose to send it. Tell us your phone model and what you heard in a GitHub issue — iPhones and older Androids are especially useful.
• Lowest lift of all: rate the touchstones we've collected — We've gathered a big pile of cultural touchstones — recognizable lines that scripts pull from — and we need help separating the wheat from the chaff. Open the rating page (https://quidam2k.github.io/conductor/rate.html) and give a quick 1–5 stars to the ones that jump out at you, good or bad. Don't rate all of them — please don't. Skip the middle: 5 stars for a line almost anyone would know and love, 1 star for one that falls flat, and leave the forgettable ones unrated (that's a signal too). Even five ratings genuinely help. No download, no typing — just tap stars and submit the prefilled issue it builds for you.
• Go deeper: make a tiny event and tell us what confused you — Open the app, create a 3–4 cue script (something simple a small crowd could do — a freeze, a wave, lights up), and note every spot that was confusing or annoying. Report the friction in a GitHub issue. You're helping us grandma-proof it — a plain-language 'this part made no sense' is worth as much as any code.

The two-minute option: rate the touchstones. Tap 1–5 stars on the lines that jump out — good or bad — and skip the middle: leave the forgettable ones unrated. No download, no account of ours, and your taps build a prefilled GitHub issue you just submit. It's the single lowest-effort way to help, and it directly shapes which touchstones we keep.

How to record voice cues (step by step)

You record right inside the app — no separate software, no account. Do it on the phone or laptop you already have.

1. Open the app: https://quidam2k.github.io/conductor/ — check the build number at the bottom of the screen matches the newest one on What’s new.
2. Load an event to record for. Easiest: tap Try the Demo to load "The Stillness," or tap Create New Event and write a short script (4–8 cues).
3. Go into the editor for that event. Next to each action you'll see a 🎤 Record button.
4. Tap 🎤 Record on an action, say the cue clearly (a second or two — "freeze", "hold", "get ready"), and stop. Tap ✓ Use & Next to keep it and move on.
5. When you've recorded every cue, go to the Review & Share step and export the recordings as a resource pack — that gives you a single .zip file.
6. Rename the .zip to something we'll recognise (like stillness-yourname.zip) and send it to us (see below).

Recording tips: somewhere quiet, normal speaking pace, keep each cue to one to three seconds (longer is fine for a clip step, where the phone plays the recording itself instead of prompting a person), and keep the volume even across cues. It plays through a phone speaker in a noisy crowd, so clear beats fancy.

What to send

• A resource pack .zip (your recorded voice cues), and/or
• An event script — either a .txt/.json file, or the plain text pasted straight into your message, and/or
• A bug report — just describe what you did, what you expected, and what actually happened.

Whatever you've got. A single recorded cue or a two-line bug note is worth sending.

Where to send it

• Open a GitHub issue and attach your file (easiest — works today, no account of ours, nothing to sign up for): open a new issue. Describe what you're sending, drag your .zip/.txt into the issue, and submit. A free GitHub account is the only requirement.
• Not sure where something goes? Open an issue on the project on GitHub and ask. No question is too small.

Coming in person instead?

We meet in person to record together roughly every couple of weeks. Can't make it? Everything on this page is designed so you can help on your own time and send it in — you don't need to be in the room.