Notification settings: independent toggles and a reminder time #27
Labels
No Label
P0
P1
P2
release-blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: null/Privacy-Period-Tracker#27
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
§29 lists six notification types, each with an independent toggle: period approaching, period expected today, "did it start?", period-end check-in, fertile window approaching, estimated ovulation. Plus a reminder time — morning, afternoon, evening, or custom.
UserPreferencesalready holdsperiodReminderEnabled,fertileWindowReminderEnabled,ovulationReminderEnabledandreminderTime, and nothing reads them either. Extend to cover all six types rather than folding them together: somebody who wants a period reminder and no fertility notifications is the common case, not an edge case, and the fertility ones are off by default for exactly that reason.The Settings screen itself is Batch 06, so this issue is the plumbing plus a minimal surface — enough to change a setting and see the reminder change, not the designed screen.
When a toggle turns on, that is the moment to ask for notification permission (§31), not before.
Changing the reminder time or any toggle must reschedule, for the same reason a forecast change does.
Verify: each of the six types can be toggled independently and the stored preferences reflect it; turning a reminder on when permission is absent prompts for it; and changing the reminder time re-enqueues the work at the new time.