Redesign Android Auto browse home with artwork and profiles #65
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?
Goal
Replace the current Android Auto browse hierarchy with the settled four-destination home and add artwork/profile switching as a dedicated implementation slice.
This is a new issue and new PR. Do not fold this work into #35 / PR #61.
Definitive product decision
The Android Auto root is, in this order:
There is no general Library root in this design.
Series ordering
The Series destination is ordered by playback recency when BookWave has playback evidence:
Books inside a series keep the existing canonical series-sequence ordering from LIB-003.
History / queue
Artwork and presentation
Android Auto browse rows should use artwork wherever BookWave has safe cached artwork:
Continue, Series, Authors and the book rows reached through Series/Authors request the host's artwork-first grid/card
content style. Profiles remains text-first/list-like so active, lock and account state stays legible.
The automotive host owns the exact background, card chrome, spacing and typography. BookWave supplies its shipped
teal platform accent where the host honours the app accent; this issue does not introduce a custom-drawn car
background.
Artwork supplied to Android Auto must be readable by the car/media host process, work from cached/offline state,
must not initiate a fresh artwork network fetch on behalf of the host, and must never expose credentials or tokens
in a URI.
Profiles
Profiles is a first-class Android Auto browse destination.
Current state to replace
Current Android Auto root on
mainis:The Library subtree currently contains Chapters, History, Downloads, Recently added, Listen again, Discover and Audio output. This issue deliberately replaces that information architecture rather than adding another tab to it.
Acceptance criteria
Ownership
Primary: Android System & Auto Agent.
Required review lenses:
Documentation
The settled product choices in this issue are recorded in
docs/product-decisions.md. Implementation details and any technical architecture needed to satisfy them may be captured in an ADR, but an ADR must not silently change the product decision.The definitive product decision for this issue is recorded as PD-001 in
docs/product-decisions.md, introduced by docs-only PR #66. PR #66 establishes the decision ledger and records the settled Android Auto root/order, series sorting, artwork target, Profiles destination, and History/Queue non-goals. This issue remains open for the separate runtime implementation PR.Physical Android Auto acceptance follow-up — 2026-09-20
The owner tested the new PD-001 browse home on the projected head unit.
Result
The Profiles destination rendered only the currently active profile even though multiple profiles are saved. The required behavior is to show all saved profiles so the driver can switch accounts from Android Auto.
Investigation
The saved-profile data source is not filtering to the active profile:
ProfileRepository.observeProfiles()is the same all-saved-profile source used by the phone profile switcher;ProfileDao.observeProfiles()selects all profile rows;The car rows were instead published with both
isBrowsable=falseandisPlayable=false. That left inactive profile rows without a valid media-hierarchy role even though they advertised theUse profilemedia-item command.Fix on PR #71
PR #71 now publishes every saved profile as:
Use profilecustom media-item command;SwitchProfileUseCaseand lock policy.Regression coverage now uses two saved profiles and pins that both rows are published, the active row is marked active, and only the inactive row advertises the switch command.
Current fix head:
0e1087d2c7a5edc2814d011d0c4a4b32d4cfb2e6.A fresh exact-head Forgejo PR verification has been dispatched; physical confirmation of the corrected multi-profile rendering remains required after the resulting build is installed.
#65 profile-row fix verification
The physical-test follow-up is now verified on the exact PR head.
0e1087d2c7a5edc2814d011d0c4a4b32d4cfb2e6verifyDebug: BUILD SUCCESSFUL in 8m 9smainThe remaining proof is physical Android Auto rendering: Profiles should now show every saved profile, with inactive rows offering the existing
Use profileaction.Canonical acceptance staging — 2026-09-24
Reviewed main / acceptance APK source:
88ae231ddc01897d83e24968bed5443ea861aeddMerged implementation: PR #71, accepted head
0e1087d2c7a5edc2814d011d0c4a4b32d4cfb2e6, merge commit3516344c3b16b8b114b6037aa68ecb30fc25d2e4.Exact-head CI: Forgejo run #187 / backend run 294 — success.
Current-main regression evidence: PR #89 exact head later passed run #270 with
verifyDebug, 2606 tests / 0 failures, clean ktlint/detekt/Android Lint/Room schema; current-main push run #271 passed at88ae231d....Acceptance matrix — repository/automated claims
content://…autoart/<token>capabilities and tests assert that server/source/token/credential material is not present in the URI.Use profilemedia-item command.SwitchProfileUseCasebefore playback handover or active-profile mutation. Locked profiles cannot be activated by the car command; the car receives a phone-unlock/permission-denied result.Historical physical failure and why it is not accepted yet
The issue records the important post-implementation failure from 2026-09-20: projected Android Auto showed only the active profile even though multiple profiles were saved.
PR #71 then changed profile rows to be host-visible browsable/non-playable items and added the multi-profile regression test. That correction is automated-green, but there is no later projected-host evidence proving that the actual Android Auto host now renders all saved profiles. This specific failure must be physically re-tested.
Acceptance APK
Forgejo Build APK run #272 produced:
bookwave-debug-0.10.6.1-2272bookwave-debug-0.10.6.1-2272.apkorg.homebord.bookwave.debug88ae231ddc01897d83e24968bed5443ea861aeddverifyDebugrerun in the artifact workflow.Residual projected Android Auto acceptance
Use at least two saved profiles.
Host-dependent matrix:
If #36 interrupts playback during this test, log it as an external #36 observation rather than a #65 failure unless the browse/profile contract itself is wrong.
Result
READY FOR PHYSICAL ACCEPTANCE