Project

General

Profile

Actions

Feature #27

open
VJ

Epic #20: Client design adaptation

Verify shared catalogue filtering on iOS

Feature #27: Verify shared catalogue filtering on iOS

Added by Vince Jurić 25 days ago.

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

0%

Estimated time:

Description

Imported from GitHub issue 269.
Source milestone: Redesign (milestone 3).
Source labels: enhancement, ready-for-human, ios.
Original state: open.

What to build

Type: HITL

Verify the completed Foods, Recipes and Guides filter flows on a supported iOS device or simulator, and fix any iOS-specific defects. This issue requires a human-accessible iOS environment. Keep evidence and fixes scoped to filtering; coordinate with existing general catalogue/typography iOS verification issues without duplicating them.

Use only the Design and Design tokens pages of https://www.figma.com/design/yisgB7iNKYtjNZdogARGIN/Bebin-prvi-meni. Exclude the reference-app page entirely. The food sheet is the visual source; recipe and guide sheets adapt its shared pattern while preserving their domain rules.

Acceptance criteria

  • Verify all three catalogues with both Serbian Latin and English copy, including long labels and larger system text.
  • The sheet and fixed actions respect safe areas, scroll correctly and remain usable with the keyboard; backdrop/close/drag dismissal follows the same draft-cancellation contract as Android.
  • Verify accessible control names, chip selected states, modal focus containment and focus return after dismissal using VoiceOver.
  • Apply, draft reset, clear-all, exact count loading/retry and zero-result states behave consistently across the three catalogues.
  • Search and filter changes reset applicable pagination; returning from details/authentication/upgrade preserves context, while the documented section reset paths clear it.
  • Verify guest, signed-in free and Premium access states without changing lock/access behaviour; record which environments were available and any unverified cases explicitly.
  • Attach screenshots or recordings and device/simulator, iOS version, locale and tested build details. Fix filtering defects found, run relevant regression checks, and explicitly document any remaining blocker.

Blocked by

No data to display

Actions

Also available in: PDF Atom