[BW-SYS-01] Expose BookWave actions to Android shortcuts and automation #23
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Classification
Planned platform-integration feature. Blocked on playback ownership prerequisites before implementation.
Product intent
BookWave should expose stable Android actions so the user can invoke audiobook behavior from launcher shortcuts, automation tools, Assistant-capable surfaces, widgets, Quick Settings and future in-app schedules without every surface inventing its own playback logic.
Concrete target: it must be possible to build a rule such as when my headset connects, continue the audiobook this phone last played.
Problem / opportunity
Android has several action surfaces but no single universal third-party automation API. Launcher shortcuts,
shortcuts.xmlcapabilities/App Actions, deep links/intents, widgets and automation apps all launch slightly different Android entry points. If BookWave implements them independently, resume ownership, profile privacy and lock behavior will drift.User value
Scope
Define one typed semantic action contract and Android dispatcher for at least:
ContinueListening— continue the book this device locally remembers, then use the shared resume-freshness policy for position.PlayPauseTogglePlaybackSkipForwardSkipBackOpenCurrentBookOpenPlayerOpenLibraryOpenSearchOpenDownloadsOpenHistoryStartSleepTimer(duration)CancelSleepTimerOpenSleepSettingsExpose appropriate actions through:
shortcuts.xmlcapabilities/App Actions where the platform supports them;All entry surfaces must dispatch into the same application/domain owners rather than directly controlling ExoPlayer or deriving their own remembered/resume state.
Security model
External automation is opt-in and narrowly scoped.
Explicitly out of scope
progress.updatedAt; BW-PLAY-01 owns remembered local book identity.Dependencies
Platform notes
Android app shortcuts are intended for specific repeatable app actions, and current Android guidance recommends keeping launcher-visible shortcuts small in number.
shortcuts.xmlcapabilities can bind supported system/Assistant actions to destinations, but are not a universal scheduler/automation interface. Therefore the semantic action contract must sit below those surfaces rather than equating 'App Actions' with automation.Storage / migration implications
None for the action contract itself. Any user-defined automation rules/schedules belong in separate issues and must name their own durable state.
Automated tests
ContinueListeningdelegates remembered-book selection and resume position to their owners.Device acceptance
Estimated effort
Medium.
Risk
Medium: an exported automation surface can become a security/privacy hole if it accepts arbitrary data or bypasses profile/playback ownership.
Recommended sequence
After GitHub #93 + BW-PLAY-01. This is the foundation for Android widgets, Quick Settings, headset rules and Garmin companion controls.
Acceptance criteria
ContinueListeningmeans the same thing everywhere.