noCV
CDOWN-102 · Describe downloads

Keep mobile download buttons consistent with durable state

Practice briefTaskIntermediate

Returning to the shelf shows Download while a transfer is active. Render controls from one persisted lifecycle.

Focused work estimate
1h 45m + prerequisites
Priority in the scenario
Medium
Engineering practice
State machines · Persistence

Estimated field mix

  • Mobile80%
  • Storage systems20%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

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

  • Active transfer shows pause
  • Completed content shows open
  • Invalid states do not expose start

Implementation constraints

  • Define explicit lifecycle transitions.

Verification to include

  • Navigate away and return
  • Load corrupt lifecycle value

Deliverables

  • Download-state projection

Rollout and recovery

Disable new downloads if state cannot be read.

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.