Feature #66
openEpic #63: Followed meal plan and Today’s meals
Show today’s meal rows on Home
0%
Description
Imported from GitHub issue 297.
Source milestone: Milestone 4.
Source labels: enhancement, ready-for-agent.
Original state: open.
What to build¶
Type: AFK
Expand the followed-plan Home summary into “Today’s meals”, showing the Current Planner Day’s actual meal slots. Use Današnji obroci in Pretplata / Danas as the design source: https://www.figma.com/design/yisgB7iNKYtjNZdogARGIN/Bebin-prvi-meni?node-id=75-6407 (parent frame 75:6369).
Use only the Design and Design tokens pages. Exclude BLW meals - referentna aplikacija. Adapt the referenced section to the agreed domain behaviour rather than introducing baby-age personalisation or individual meal completion.
Acceptance criteria¶
- Home shows the followed plan’s current-day meals, with a “Today’s meals” heading and “Full day” link opening that exact plan/day. Browsing other plans or days does not change the Home source.
- Render actual ordered meal slots and planned items with their localised meal type/custom label, title, description and data-supplied thumbnail where available; support variable slot/item counts and existing fallback behaviour without invented food illustrations or nutritional claims.
- Reuse existing components, semantic tokens and typography to match the reference’s row structure, circular thumbnail treatment, spacing and dividers. Inspect implementation assets against the design; do not ship temporary Figma URLs.
- Retain whole-day completion only. Do not add the reference’s per-meal ticks, strike-through state or “Pojedeno” sticker, since no per-meal completion model exists.
- Use the revised shared Current Planner Day mechanism. Subscribe to Firestore followed-plan/position/schedule changes; refresh on Home focus, foreground return and date changes in the shared schedule time zone; account progress/content changes and plan reset must be reflected without using stale Selected Planner Day state.
- With no followed choice, show “Choose a meal plan”. Handle loading, retryable error and unavailable followed-plan states; hide unavailable content and offer “Choose another plan” without silently switching.
- Respect Premium and guest/free access, authentication changes and content lifecycle updates; do not leak locked meal details or another account’s selection/progress.
- Provide Serbian Latin and English copy, accessible controls and readable layouts at small widths and large text sizes.
- Test source selection, current-day refresh, completion/reset changes, navigation, access and exceptional states. Visually verify the requested block against Figma on available native targets, record evidence and any platform verification limitation, and update Home/domain documentation. Leave unrelated Home layout differences outside scope.
Blocked by¶
Shared-state revision — 4 November 2026¶
This replaces the earlier device-local followed-plan/current-position decisions. ADR 0023 and the planned revision in the reminder specification are authoritative.
- Two signed-in devices show the same followed plan/current day after synchronisation. Each device’s notification opt-in does not change Home’s source or calendar progression. Guests retain local state; account transitions never leak another account’s choice.
- Verify updates after remote switch, stop schedule, progress reset and shared-zone date rollover, including loading/error states before shared state is resolved.
Acceptance evidence — 4 November 2026¶
The nine original criteria and the remote-update verification criterion are supported by automated checks and recorded Android presentation evidence. Native evidence covers Serbian Latin/English, actual public meal imagery, locked content, small widths and enlarged text. Remote switch/stop/reset and shared-zone rollover checks are automated. The two-signed-in-device acceptance item remains unchecked pending hosted end-to-end synchronisation verification. Physical two-phone, iOS and native screen-reader operation are not claimed. The fresh Figma transport failed; comparison used the previously obtained reference for the same Design node. Current validation: 715 client Vitest tests, 10 Node release checks, TypeScript and lint pass. Implementation is not deployed.
No data to display