[BW-AUTOMATION-01] Add headset-triggered Continue automation #25
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 Android automation feature. Blocked on #23 and #24.
Product intent
Allow a user-defined rule such as: when this headset connects, continue the audiobook this phone last played.
This should be a native BookWave automation built on the same semantic action contract exposed to Android, not a second playback implementation.
Scope
ContinueListeningthrough #23.Explicitly out of scope
Dependencies
Storage
Persist user automation settings and selected device identities using stable Android identifiers only where the platform actually provides them. If identity is unreliable on an Android version/device class, prefer a broader explicit rule such as 'any headset' over pretending certainty.
Privacy / security
No book metadata in Bluetooth rule storage. A locked profile must obey the same playback/metadata policy as invoking Continue manually.
Automated tests
Device acceptance
Test wired headset where supported, Bluetooth headset, reconnect after process death, screen off, profile switch, and a car/A2DP device to confirm the rule does not accidentally broaden into car behavior.
Effort
Medium.
Risk
Medium. Auto-play is useful but can be obnoxious if device matching or audio-focus policy is loose.
Acceptance criteria