Permission is the gate, and asking at the wrong moment earns a permanent no. Ask in context, from notification settings or an affordance the user just interacted with, never on first load. The spec doesn't pin the timing; settle it here and feed it back.
Spec
- Push - the subscription lifecycle
Acceptance criteria
- The permission prompt is user-initiated, never fired on first load
- Denial leaves a working app with a re-enable path in settings
- Disabling push in settings unsubscribes and deregisters with the server
- The chosen timing rules are documented in the spec before this closes
Blocked by the registration ticket and #75.
Permission is the gate, and asking at the wrong moment earns a permanent no. Ask in context, from notification settings or an affordance the user just interacted with, never on first load. The spec doesn't pin the timing; settle it here and feed it back.
Spec
Acceptance criteria
Blocked by the registration ticket and #75.