Permissão pedida no momento certo, deep links, horas de silêncio.
Spec — Push notifications
Status: draft · Created: 2026-11-10
1. Context and goal
Users get timely notifications they agreed to receive, which open the right screen and respect the hours they want to be left alone.
2. Functional requirements (EARS)
- FR-1: THE SYSTEM SHALL ask for notification permission only after the user takes an action that benefits from it, never on first launch.
- FR-2: WHEN the user declines permission, THE SYSTEM SHALL not ask again for at least 30 days.
- FR-3: WHEN the app gets a push token or the token changes, THE SYSTEM SHALL register it on the server within 5 seconds, and remove tokens the push service reports as invalid.
- FR-4: WHEN the user taps a notification, THE SYSTEM SHALL open the screen named by its deep link within 2 seconds, including from a cold start.
- FR-5: WHILE the user's quiet hours are active in their time zone, THE SYSTEM SHALL hold non-urgent notifications and deliver them when quiet hours end.
- FR-6: THE SYSTEM SHALL let the user turn each notification category on or off, and send none from a category turned off.
- FR-7: THE SYSTEM SHALL send a user at most 5 non-urgent notifications per day.
3. Out of scope
- SMS and email notifications.
- Rich media notifications with video.