Feature #59
closedEpic #20: Client design adaptation
Adapt Home food-introduction progress to the Figma grid
0%
Description
Imported from GitHub issue 291.
Source milestone: Milestone 3.
Source labels: enhancement, ready-for-agent.
Original state: closed.
What to build¶
Deliver the Home food-introduction category grid using pastel tiles and live account counts. Each tile opens Foods filtered to its category. Preserve public catalogue caching and account progress boundaries, including guest, loading and retry behaviour. This slice includes implementation, localisation, tests and Android verification.
Design sources and scope¶
Use only the Design and Design tokens pages in https://www.figma.com/design/yisgB7iNKYtjNZdogARGIN/Bebin-prvi-meni. Home references: Guest 69:719, signed-in free 75:4348, Premium 75:6369. Exclude the reference-app page entirely.
Adapt presentation while preserving the current domain and ADRs: Home remains Početna / Home; no baby-age collection, personalisation, daily dashboard, content feeds, global selected plan or per-meal completion. Retain the shared header and bottom tabs without duplicating the design's content header. Reuse existing tokens, typography and controls. Reference layout: 390-unit width, 20-unit gutters and 24-unit section spacing; adapt to device width and text scaling.
Acceptance criteria¶
- The grid shows every category containing at least one food; it does not hard-code six categories or sample totals.
- Tiles use category surfaces and compact count/category presentation from Figma; the reference width supports three columns, reducing columns when width or text scaling requires it.
- Signed-in users see account-owned introduced counts; guests see unknown counts such as —/20 plus the existing contextual sign-in action, without invented personal progress.
- Each tile opens the Foods catalogue with its category filter; category labels and count copy respect the selected locale and existing fallback rules.
- Initial loading, no non-empty categories, catalogue failures and personal-progress failures render coherently; unknown or failed personal progress is not presented as a genuine zero count.
- Previously loaded categories remain visible during revalidation/failure; explicit retry, warm-cache reuse, foreground invalidation and shared-request protections remain intact.
- Meaningful tests cover access states, filtered navigation, loading/error/retry and cache regressions; client tests, type checking and lint pass.
- Android verification covers guests/free/Premium, both locales, narrow widths, enlarged text and accessible tile announcements, with recorded evidence.
Blocked by¶
None - can start immediately.
Execution type¶
AFK — ready for an agent.
Implementation and verification — 2 November 2026¶
All eight acceptance criteria pass. Home now uses responsive pastel tally tiles: three columns at reference width, two/one as width or text scaling requires, all current non-empty categories, account-confirmed counts and unknown guest/loading/error progress. Personal-progress retry resubscribes independently of the public catalogue; late callbacks are ignored after replacement/account changes. Existing catalogue cache safeguards are preserved.
Final client verification passed 76 Vitest files / 627 tests, Node guards, type checking, lint and whitespace validation. Native Android evidence covers 30 access/locale/size cases, 12 loading/empty/error cases, real filtered navigation in both locales, root-filter reset and generated TalkBack speech for known/unknown progress. Guest/free/Premium presentation uses a production-component fixture without changing the real account entitlement; actual signed-in Home and Foods were checked separately. TalkBack captions verify generated speech text; acoustic pronunciation/full physical gesture traversal are not claimed.
Report: docs/home-progress-acceptance-291.md. Evidence: docs/evidence/home-291/, indexed by matrix.json, geometry-summary.json, states.json, talkback.json and final-checks.json. Device/accessibility settings and capture protection are restored. Temporary app route removed; changes remain uncommitted. This update does not close the issue. iOS verification remains in GitHub 293.
No data to display