In the Android project, Assistant or shortcut entries exist for several actions. The ones that are strictly confirmed and clearly wired into the Explore context are mainly:
start the Discover Tour
show nearby spots
show upcoming events
play audio
pause audio
stop audio
The code currently contains these German shortcut labels among others:
Tour starten
Eine Entdeckungstour starten
Audio abspielen
Den Audioguide pausieren
Den Audioguide stoppen
In der Nähe
Spots in der Nähe anzeigen
Veranstaltungen
Kommende Veranstaltungen anzeigen
Important for users:
For Google Assistant, we should phrase the public help more carefully than for Siri.
The code clearly contains shortcut names and intent targets, but not the same explicit list of natural spoken phrases that we have for Siri.
Because of that, public help should talk about Google Assistant shortcuts or Assistant actions instead of promising exact spoken sentences.
Audio commands are most useful when a matching playback session is already active.
Important technical review note:
In the Android project, Start Discover Tour also has an explicit Assistant feature binding.
The general flows for Discover Tour, Nearby and Events are clearly connected in the Explore context.
Audio commands are also connected directly.
Additional shortcut entries such as Stop tour, Next spot or Previous spot do exist as shortcut definitions, but in the current Android code I do not see the same clearly confirmed UI connection as for Start Discover Tour, Nearby and Events. We should therefore only document them firmly after a short product test.
This makes myTuur usable not only by touch, but also through voice and quick actions.
