Short answers to common questions. For anything not here, email hello@mymc.app and we’ll get back to you within a day.
Getting started
Install the iOS app, sign in with Apple (recommended) or email/password, and tap the red record button on the Map tab to capture a ride. The first time you record, iOS will ask for location, motion, and notification permissions — say yes to all three for full functionality.
Voice nav isn’t playing
- Check Settings → Voice → Spoken turn-by-turn is on.
- Voice prompts route to the phone’s active audio output. If your helmet intercom is connected via Bluetooth, prompts come through it; music ducks automatically.
- The first prompt fires around 400 m before the turn; if you’re inside that distance when the route starts, the first prompt is the “in 30 m” one.
Crash detection caveats
The crash detector watches for sustained tilt, high g-force, and a stopped state. It triggers a countdown you can cancel before SMS goes out. It will miss some crashes and will occasionally false-fire (Settings → Safety → Low sensitivity if it’s too eager). It is not a replacement for calling emergency services directly.
GPX import / export
Library → Import GPX accepts standard GPX 1.1 files up to 10 000 points. After recording a ride, tap Share GPX on the trip detail screen to AirDrop or save the file. Shared route URLs (mymc.app/r/…) open the public preview page when the rider has marked the route unlisted or public.
Sync isn’t working
- Pull to refresh on the Library tab.
- New rides upload in the background once GPX serialisation finishes — for a long ride that can take a few seconds.
- Check Settings → Backend → API endpoint matches your environment (default is fine in production).