Booka Ducka Ding Dong · support

Oh, duck.

If the route, story, or audio misbehaved, stop somewhere safe first. Then we can debug the weird little beast.

Booka is entertainment, not turn-by-turn navigation. Do not follow a story choice into traffic, a closed path, private property, unsafe terrain, or anywhere local signs and judgment say not to go. Buttons remain the manual fallback.

Owner-only beta, disclosures reviewed September 22, 2026. Story Lab, Apple sign-in and the restricted owner Library are for private testing. Use the current qualified TestFlight build for matching controls. A private story becoming ready to listen is not public publication or a claim of human editorial approval. Public creator submissions, creator payments, and external distribution remain closed.

01Fast fixes

No route: verify Location is allowed While Using the App, move outdoors, wait for a better location fix, and try a shorter route.
Route after a choice: the old line and instructions should disappear, rerouting should appear, a new route should begin at current GPS, and a loop should keep the original start as its finish. If recovery stalls, pause somewhere safe, recenter, and wait. Build 6 retries and may honestly fall back directly to the original finish.
No voice: check the in-app narration status and your network. Booka may offer the system voice when ElevenLabs is unavailable.
Playback speed: choose 0.75×–2× from the player. ElevenLabs audio changes immediately; an Apple system voice applies the new rate on the next chapter.
Unexpected ambience: turn off Settings → Play ambience during pacing gaps. The local procedural sound should stop when narration resumes.
Offline replay is silent: reconnect and retry the story’s download. Prepared Library audio does not require permission for new AI generation. Custom stories that need new ElevenLabs audio do require separate narration permission. Check the displayed source or error before changing settings.
Old story resumed: Settings can remove the unfinished checkpoint without deleting completed Library stories.

02Send a useful report

Email daniel@frwrd.team with “Booka support” in the subject and include:

App version/build and iPhone/iOS version.
Whether it was Featured, archived, or custom; loop or destination; Buttons or Movement.
The direction selected or physically taken, whether the old line disappeared, the Library route-update count, and whether the new remaining distance began decreasing.
What you expected, what happened, and whether retrying changed it.
The exported story-history JSON, if it is relevant and you deliberately choose to share it.

Do not send your home address, precise route, full story transcript, provider key, or unrelated personal information.

03Privacy and content

Use Privacy Choices for permission, deletion, and export help. An in-app content-report action is not available yet. You can email daniel@frwrd.team with the story title or revision and concern, without pasting the whole work.

The proposed reporting, copyright and appeals process explains which public controls still need to be completed. Support email is available; a registered copyright-agent process is not claimed.

04Current beta limits

The beta does not promise route-native intersection binding, flawless adaptive revision, perfect pacing estimates, flawless Movement inference, multi-hour stories, cross-device Library sync, billing, a new quest every day, or public creator publishing. Those features stay out of public claims until their tests pass.

One address, no form

Say hi.
Or complain.

daniel@frwrd.team