One channel. Every rider. No pairing.
Demo mode — sign-in connects for real once an API key is added in the Admin Panel (Step 4).
Enter the 4-digit PIN to open the Admin Panel.
You're not in any servers yet.
Everything already works for free with no keys. Paste keys in here as you get them — nothing changes until you do, and I'll ask before suggesting anything paid.
Unlocks real Directions and Street View (Step 5). Until then, free OpenStreetMap tiles are used.
Powers real road directions on the free map (Step 14.5) without needing Google billing. HERE's free tier (250k requests/month) needs no credit card — sign up at developer.here.com. Leaves the OSRM public demo server as an automatic fallback if this is empty or a request fails.
Needed only for the music player's search box (finding songs by name). Playback itself works with no key at all. Get a free key at console.cloud.google.com — enable "YouTube Data API v3", then create an API key.
Unlocks real Google Sign-In (Step 6) and real live location sharing between riders' devices (Step 7). Free tier is enough to start.
Only needed for the packaged Android app (Phase 4, Step 1): the "Web client ID" Firebase auto-created in Google Cloud Console when Google Sign-In was enabled above. Lets the app's native Google Sign-In hand its token to Firebase. See the Android project's README for exactly where to find it.
Only needed for Step 8's real group audio if free Google STUN isn't reliable enough on cellular data. This is usually a paid service — I'll ask you before recommending one, this is just where it plugs in once you decide.
Points the app's "Updates" tab (Step 18) at your GitHub repo's Releases, where the cloud build (Step 17) already publishes a signed APK plus a version.json on every push. Enter it as yourname/talk-on-the-go-android — pasting the full github.com URL also works.
Only needed if that repo is private (Step 20) — leave blank for a public repo. Use a fine-grained personal access token scoped to just this one repo, with "Contents" set to Read-only and nothing else, and give it an expiration date. This token is stored on the device (like the other keys above) and used only to fetch release files — treat it as sensitive, and revoke/rotate it on GitHub any time you suspect it's leaked.
Saved keys are stored only in this browser (not uploaded anywhere). On your live Hostinger site, paste the same values in once there — each browser/device keeps its own copy.