Feature #68
openEpic #63: Followed meal plan and Today’s meals
Let users stop following a meal plan without losing progress
0%
Description
Imported from GitHub issue 300.
Source milestone: Milestone 4.
Source labels: enhancement, ready-for-agent.
Original state: open.
What to build¶
Type: AFK
Let users stop following their current meal plan without selecting another plan.
Add the action beside the current Following this plan status on the plan screen.
Use Stop following this plan in English and Prestani da pratiš planer in Serbian Latin.
Remove the followed-plan selection and stop its shared schedule.
Cancel notifications on this device.
Other devices cancel notifications when they receive the shared change.
Preserve completed days and the retained Current Planner Day for that plan instance.
Home then shows Choose a meal plan / Izaberi planer.
Users can follow the same plan again later.
Related work: GitHub 295, GitHub 296 and GitHub 297.
Keep plan switching and progress reset as separate actions.
Acceptance criteria¶
- Show the action beside the following status for the currently followed plan.
- Support signed-in free users, Premium users and guests with an existing followed choice.
- Preserve existing access rules for plan content.
- With an active shared schedule, show a confirmation before making changes.
- Explain that stopping follow ends the schedule and preserves progress.
- Explain that other devices cancel notifications after synchronisation.
- Explain that disconnected devices can deliver previously scheduled notifications until they receive the change.
- Leave all state unchanged when the user cancels confirmation.
- Without a schedule, perform the action without an additional confirmation.
- Clear the account followed-plan reference and its shared schedule consistently in Firestore.
- Report success only after server acknowledgement.
- For guests, clear the device-local followed choice without creating account data.
- Cancel pending notifications for the removed followed plan on this device.
- Clear or invalidate local delivery state so stale tasks cannot recreate its notifications.
- Let other signed-in devices update Home and cancel notifications when they receive the shared change.
- Preserve completion records and retained Current Planner Day values for all plan instances.
- Do not delete meal-plan content, account data or unrelated notification requests.
- Show Izaberi planer / Choose a meal plan on Home after success.
- Remove stale meal rows immediately when the followed choice disappears.
- Let the user follow the same plan again with preserved progress and position.
- Keep notifications off until the user explicitly enables them again.
- Handle repeated requests safely without duplicate changes.
- Prevent a stale unfollow request from clearing a different plan or a newer schedule.
- Handle account changes without modifying another account's followed state.
- Disable duplicate submissions while saving.
- Show the existing retryable error presentation when saving fails.
- Provide recovery when notification cancellation fails after the shared change succeeds.
- Do not restore an old shared schedule during recovery.
- Provide accessible controls and confirmation copy in Serbian Latin and English.
- Verify schedule confirmation, cancellation, no-schedule removal, failures, retries, account changes and concurrent plan changes.
- Verify preserved progress, Home updates, notification cancellation and following the same plan again.
- Verify shared updates across two signed-in clients where available.
- Record native verification evidence and any platform or synchronisation limits.
- Update domain documentation and the followed-plan decision with the removal behaviour.
Blocked by¶
None. The existing followed-plan and shared-schedule implementation supplies the integration points.
No data to display