Project

General

Profile

Actions

Feature #21

closed
VJ

Epic #20: Client design adaptation

Adapt client screen headers to Figma title and navigation patterns

Feature #21: Adapt client screen headers to Figma title and navigation patterns

Added by Vince Jurić about 1 month ago.

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

0%

Estimated time:

Description

Imported from GitHub issue 264.
Source milestone: Redesign.
Source labels: enhancement, ready-for-agent.
Original state: closed.

What to build

Adapt client screen headers to the two header patterns in the approved Figma design. Main tab screens currently use the same compact h4 navigator title styling as detail screens; they should instead present large, left-aligned screen titles, while detail screens use the compact, centred navigation bar.

Deliver this as one end-to-end client change covering shared header presentation and adoption across existing routes. Use existing design tokens and preserve route-specific actions, back navigation, accessibility, localisation and access behaviour.

Type: AFK. Follow-up to the completed Client design adaptation milestone (GitHub 253–GitHub 256).

Design sources and measured evidence

  • Use only the Design and Design tokens pages in https://www.figma.com/design/yisgB7iNKYtjNZdogARGIN. Exclude the reference-app page completely.
  • Main tab titles: Schibsted Grotesk SemiBold, 32 px / 40 px line height (Display/h1-600), 20 px horizontal inset and generally 16 px top spacing within the content safe area.
  • Compact navigation: Top bar component, Manrope SemiBold 16 px / 24 px (Text/16-600), centred title, equal 44 px leading/trailing slots, 8 px gaps and 20 px horizontal insets. The design has 31 instances.
  • The source component is 58 px high, but its declared 16 px top + 12 px bottom padding plus 44 px slots require 72 px. Rendered slots start at y=9. Preserve the visible default geometry (58 px content bar, 44 px slots, 9 px top / 5 px bottom clearance), rather than copying the conflicting declared padding. Add device safe-area clearance separately; allow the bar to grow for text scaling.
  • Guest Home title starts at y=18 versus y=16 on most tabs. Use the common 16 px spacing for ordinary tab titles; retain intentional compound content such as a subtitle separately.

Current domain docs govern wording and available flows. Keep Home, Foods, Recipes, Guides, Meal Plans, Profile and other current localised labels; do not introduce baby profiles, age onboarding, password authentication or other obsolete Figma flows. Do not replace article/content titles with navigation titles.

Acceptance criteria

  • Home, Foods, Recipes, Guides and Meal Plans use a consistent large, left-aligned title with the existing h1 token and 20 px horizontal inset, without duplicate navigator/content titles.
  • Existing detail, Profile, Premium/subscription, Settings and legal navigation headers use the compact Manrope 16/24 title pattern where applicable; existing authentication and language-onboarding titles retain their distinct screen-title hierarchy.
  • Compact titles remain centred when either side has no action or a different action. Existing profile access, back/close controls and route-specific actions remain usable, with touch targets at least 44 × 44 px.
  • The compact bar resolves the source sizing conflict as described above, accounts for safe areas exactly once, and supports larger font settings without clipped or overlapping text or controls. Long localised titles have an intentional wrapping or truncation treatment.
  • Reuse shared header styling/components and existing typography, colour and spacing tokens; avoid per-screen copies of header geometry.
  • Preserve Serbian Latin and English labels, current product flows, loading/error presentation and Guest/Free/Premium behaviour.
  • Verify representative tab, detail, Profile/Settings and Meal Plan action headers in both locales, including back navigation, an absent trailing action, a long title and increased font size. Record screenshots or rendered evidence where available and clearly identify any native verification that remains outstanding.
  • Run relevant client type/lint checks and focused behavioural tests for changed navigation or header actions; do not add tests that merely repeat style constants.

Blocked by

None — can start immediately. Earlier token and typography adaptation (GitHub 253–GitHub 256) is complete.

Scope boundary

Client header adaptation only. Editing Figma master components or attaching missing Figma text styles is separate design-file maintenance and is not required for this implementation.

Acceptance verification — 16 October 2026

All eight acceptance criteria verified against the current working-tree implementation. Changes are not yet committed or merged.

Criterion Evidence
1. Large tab titles without duplicates Shared h1 tab header; duplicate Home/catalogue titles removed; all five tabs recorded in both locales.
2. Compact navigation and preserved onboarding hierarchy Root and legal stacks use shared Manrope 16/24 headers; authentication/onboarding retain their existing header-free layouts.
3. Centring and usable actions Equal 44 dp side slots; native Profile/back navigation and Meal Plan action presence; focused tests cover custom leading actions, direct-link fallback and disabled callbacks.
4. Geometry, safe areas and larger text 58 dp minimum bar, 9/5 dp clearance; native safe-area bounds; long titles tested in both locales at 100% and 150%, with two-line tail truncation and increased bar height.
5. Shared components and tokens Shared ScreenHeader/StackScreenHeader reuse existing typography, colour, spacing and touch-target tokens. Source-specific bar clearance is documented centrally.
6. Localisation, flows and access states Existing labels and business logic preserved; full client regression suite passes.
7. Representative native evidence 32 recorded Motorola edge 50 pro / Android 16 cases and four screenshots; both locales, navigation, absent trailing action, long titles and larger text covered.
8. Checks and behavioural tests Fresh client typecheck and lint pass; all 408 tests across 57 files pass. New tests exercise headings, navigation and action behaviour.

Evidence is saved in docs/screen-header-acceptance-264.md, docs/evidence/headers-264-native.json and docs/evidence/headers-264/ in the working tree.

Native iOS rendering, gestures and safe areas remain unverified and are explicitly documented, as required by criterion 7. The live Android account was Premium; Guest/Free invariants are covered by automated regression tests. Synthetic action checks did not reset real progress. Device language/text size were restored and the temporary test route was removed.

No data to display

Actions

Also available in: PDF Atom