Project

General

Profile

Actions

Feature #39

closed
VJ

Epic #20: Client design adaptation

Verify onboarding on Android

Feature #39: Verify onboarding on Android

Added by Vince Jurić 23 days ago. Updated 21 days ago.

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

0%

Estimated time:

Description

Imported from GitHub issue 286.
Source milestone: Milestone 3.
Source labels: enhancement, ready-for-human.
Source state as of 30 October 2026: closed.

What to build

Verify the shipped language-selection and app-introduction journeys on Android using supported development/release builds. Record native acceptance evidence and resolve discovered defects. This is a HITL slice because it requires native devices/builds and accessibility interaction.

Acceptance criteria

  • Verify fresh-install language -> introduction -> Home, and an upgrade with an existing language preference that bypasses the introduction, without losing the selected language.
  • Verify both locales, device-locale preselection, immediate language preview, Next/Back, Skip on each slide and Finish. Completed onboarding does not reappear after relaunch or account changes.
  • Kill/relaunch during the introduction and verify the last saved step resumes. Verify error/retry behaviour with controlled storage failures where practical, identifying any automated-only evidence.
  • Compare against Design nodes 200:4297, 71:2831, 71:2852 and 71:2872, allowing documented product-copy and responsive adaptations. Check illustrations, typography, selected rows, progress and action placement.
  • Check small portrait screens, increased system text sizes, top/bottom safe areas, Android system Back and TalkBack reading/focus order, selected language state, step announcements and touch targets.
  • Verify the existing online-required gate and app-wide capture protection still apply. Use permitted acceptance tooling/evidence without weakening production protection.
  • Record platform/build/device details, outcomes and evidence in the established repository acceptance-document format. Fix defects and recheck affected paths; explicitly record any remaining blocker rather than claiming unperformed native verification.

Design sources and scope

Use only the Design and Design tokens pages in https://www.figma.com/design/yisgB7iNKYtjNZdogARGIN/Bebin-prvi-meni . Exclude the reference-app page entirely.

Approved scope: any number of code-defined onboarding flows, each with any number of screens. The initial product flows are language selection followed by a skippable app introduction. No remote flow editor, analytics, account requirement, baby profile, baby-age collection or subscription setup is introduced. Preserve existing online-required and screen-capture protection policies.

Blocked by

Acceptance verification — 29 October 2026

Criteria 1, 3, 4 and 7 are verified and checked. Evidence is committed in be4c062 on codex/286-android-acceptance: docs/onboarding-android-acceptance-286.md and docs/evidence/onboarding-286/. Criterion 3 uses native resume evidence plus explicitly identified automated-only storage failure/retry tests. Criterion 7 records build/device details and unresolved blockers; checking it does not imply those blockers are resolved.

Follow-up results (30 October 2026):

  • 2 — verified 30 October: real Google sign-in, signed-in relaunch and sign-out preserved English and the exact completed onboarding state; Home appeared without replay. Combined with the existing locale/navigation evidence, criterion 2 is checked. Account identity is omitted from repository evidence.
  • 5 — verified 30 October: the user completed physical TalkBack traversal of language selection and all three introduction slides. Heading/body order, selected language, step announcements, action labels and Back passed; no missing/repeated items or decorative artwork/dot stops. Combined with prior small-screen/text/safe-area/target evidence, criterion 5 is checked.
  • 6 — verified 30 October: the offline gate passes the recorded Android rechecks. The development capture exception was removed to match the documented all-build policy. Android reports a secure application window; the user confirmed a blank Recent apps preview, blocked screenshots and hidden app content in screen recordings. Criterion 6 is checked. Verification used the development build with protection enabled; no separate preview/store binary was tested. Eight focused capture tests, lint and TypeScript pass.

83 focused tests passed. Temporary device settings and onboarding/language preferences were restored. Issue remains open.

All seven acceptance criteria are now checked. The dated follow-up is recorded in docs/onboarding-android-acceptance-286.md with capture evidence in docs/evidence/onboarding-286-follow-up/. No PR has been created yet; the issue remains open pending delivery. iOS acceptance remains in GitHub 287.

VJ Updated by Vince Jurić 21 days ago Actions #1

  • Description updated (diff)
  • Status changed from To Do to Done
Actions

Also available in: PDF Atom