Project

General

Profile

Actions

Feature #74

open
VJ

Verify Meal Plans and account token accessibility and presentation on iOS

Feature #74: Verify Meal Plans and account token accessibility and presentation on iOS

Added by Vince Jurić 11 days ago.

Status:
To Do
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Imported from GitHub issue 262.
Source labels: ready-for-human, ios.
Original state: open. No source milestone.

Parent and scope transfer

Follow-up to GitHub 256 — Adapt Meal Plans, authentication and settings to Figma tokens.

The user explicitly moved native iOS accessibility/presentation verification out of GitHub 256 on 16 October 2026. Android verification and manual browser production-component checks remain in GitHub 256; this issue owns the outstanding iOS portion of its platform acceptance criterion. This is verification and fixes for the existing implementation, not a new iOS reminder feature or a dark theme.

What to verify

Use an actual iOS build on an iPhone/iPad or simulator. Inspect only the Design and Design tokens pages of Figma file yisgB7iNKYtjNZdogARGIN; exclude BLW meals - referentna aplikacija. Use the single-mode Palette, Roles and Scale collections and text/effect styles recorded in GitHub 253.

Scope: Meal Plan age selection/day chips, selected/completed/locked combinations, completion controls, introduction and Premium badges, reminder setup/settings controls, provider sign-in and terms, Premium/restore/activation wrappers, Profile and Settings language controls. Preserve account, subscription, locale and reminder behaviour. Native alerts, provider sheets and RevenueCat/store UI have platform/SDK-owned presentation; document that ownership instead of claiming client tokens control them.

Reference artefacts from GitHub 256's implementation working tree:

  • docs/design-state-inventory-256.md
  • docs/meal-plan-account-token-acceptance-256.md
  • apps/client/scripts/meal-plan-token-device-acceptance.tsx

Acceptance criteria

  • Record iOS version, device/simulator model, build/commit, locales (sr-Latn and en) and text-size settings; verify an installed native build rather than treating export or React Native Web output as iOS rendering evidence.
  • Verify touch targets of at least 44 logical units, spacing, radii, icon geometry, semantic colours, foreground/background contrast and applicable existing effects across the scoped screens.
  • Verify default, selected, completed/checked, selected+completed, pressed, disabled-off, disabled-on, busy/loading, error and locked states where applicable. Locked days must remain actionable for the existing access flow; saving must not erase checked state.
  • Check VoiceOver names, roles, checked/selected/disabled/busy state and announcements, reading order, focus movement, modal entry/dismissal and return of focus. Check hardware-keyboard focus/activation where supported; verify the shared web Space-key fix does not regress native controls.
  • Check normal and enlarged Dynamic Type and narrow/landscape layouts in both locales. Long day/food titles, badges, legal acceptance, provider labels, reminder fields/errors and Premium actions must remain readable and reachable without overlap or unintended clipping.
  • Check Apple sign-in availability/presentation, terms gating, Premium wrapper/restore/error/activation states, Settings locale selection and reminder modal presentation while preserving existing application logic. Do not initiate real purchases or mutate real progress merely to test presentation; use controlled fixture/service states where necessary.
  • Preserve the current iOS reminder-unavailable state and document it. Implementing iOS notification delivery remains in GitHub 242 and is outside this verification issue.
  • Save screenshots and accessibility/interaction observations in the acceptance documentation, fix discovered regressions, and run client typecheck, lint and relevant regression tests for any code changes. Record unperformed checks explicitly and leave their boxes open.

Preconditions and related work

Requires the GitHub 256 implementation in an iOS test build and access to Xcode/iOS device or simulator. Typography-wide native acceptance remains in GitHub 258; catalogue/detail-specific iOS styling remains in GitHub 260. Do not duplicate or silently close either scope.

Implementation type: HITL.

No data to display

Actions

Also available in: PDF Atom