Distinguish unknown course-download sizes from zero bytes
Unmeasured courses show 0 MB and users assume downloads are free of storage cost. Display size uncertainty.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Formatting · UX
Estimated field mix
- Mobile100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional learning app Birch offers synthetic text and small local media fixtures through a loopback adapter. No copyrighted course assets or network accounts are needed.
Setup prerequisites
- Create small local byte fixtures and a range-response stub.
- Simulate low storage, interruptions and stale manifests.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Unknown size is labeled
- Zero-byte fixtures remain valid
- Unit formatting has boundary tests
Implementation constraints
- Do not invent estimates without metadata.
Verification to include
- Render zero and unknown
- Render malformed size
Deliverables
- Size formatter and shelf states
Rollout and recovery
Fall back to byte counts for known values.
Value of the work
For the engineer: Practice mobile file lifecycles and background state recovery.
For the team: Inspect predictable resource usage and truthful download status.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.