[BW-DL-08] Show active download queue and live progress in screen and notifications #29
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 download UX implementation. Depends on #17-#19 for truthful recovery/execution state.
Product intent
Make downloads observable while they are happening.
The Downloads screen should show which books are currently downloading, queued, paused, retrying or waiting, with live progress. Android notifications should also show useful download progress while work is active.
Current gap
BookWave already has a Downloads management screen and
BookDownloadWorkerforeground progress notification, but the two surfaces do not share a first-class live progress model:User value
A listener can answer:
Scope — Downloads screen
Restructure/evolve the existing Downloads screen into two conceptual areas:
Active / pending
Rows for Queued, Running, Waiting, Retrying, Paused and Failed/recoverable work as defined by #17/#19.
Each visible/authorized row should show:
Title-hidden rows retain generic metadata privacy.
On device
Keep completed stored copies/device storage management separate from active transfer status. Do not lose pin/remove/verify/storage-location functionality.
Scope — live progress contract
Scope — notifications
While downloads are active:
Recommended privacy default: notification may say
Downloading 2 books · 42%or generic BookWave download status without exposing book titles on a locked device. If title-bearing notifications are later offered, they must obey explicit privacy/lock settings.Explicitly out of scope
Dependencies
#20 removable-storage work may enhance states later but does not need to block the basic active queue.
Android platform review
Before implementation, re-check the current Android/WorkManager guidance for long-running/user-initiated downloads, foreground notification requirements and Android 16+ job quotas. Do not change the execution architecture in this UI slice unless the current implementation is actually incompatible or materially harmful.
Storage / migration
No Room migration expected for live progress. Durable file/manifest state remains existing download storage. WorkManager remains transient execution evidence.
Privacy / security
Automated tests
Device acceptance
Estimated effort
Medium.
Risk
Medium because multiple WorkManager workers, foreground notifications and UI state must agree without becoming duplicate state owners.
Sequence
After #17-#19. High-value download UX follow-up.
Acceptance criteria