Port existing screens to Expo Router

james commented

2026-06-20 15:44:35 +00:00

Owner

Port the remaining screens from app/(app)/, app/login, app/register, app/page.tsx, and app/offline/page.tsx to Expo Router in apps/client.

Per-screen subtickets are too granular; this is one ticket with a checklist. Each item is a self-contained port — read the current Next.js page, render the same UI in apps/client using DS primitives + tokens, replace data fetching with the generated client + hooks.

Scope

Port each screen, preserving its current behaviour and tests where applicable.

/ (home / landing)
/login
/register
/profile
/skills
/experience
/settings
/notes (the TanStack reference route)
/offline (force-static today; document the Expo equivalent)
Any 404 / error pages

Acceptance criteria

Every existing route from app/ is reachable in the Expo client.
Cross-user isolation behaviour (404 on someone else's data) verified end-to-end on at least Skills and Profile.
No screen reads from apps/api source — all data flows through packages/api-client.
Visual parity on both themes.
i18n: strings load via the new runtime; placeholder text and ARIA labels survive.

Out of scope

Deleting the Next.js UI files (its own ticket — easier as a single cleanup PR).
New visual designs — this is a port, not a redesign.

Composes with

Expo scaffolding, Decommission Next.js UI.

Part of

#176

Port the remaining screens from `app/(app)/`, `app/login`, `app/register`, `app/page.tsx`, and `app/offline/page.tsx` to Expo Router in `apps/client`. Per-screen subtickets are too granular; this is one ticket with a checklist. Each item is a self-contained port — read the current Next.js page, render the same UI in `apps/client` using DS primitives + tokens, replace data fetching with the generated client + hooks. ## Scope Port each screen, preserving its current behaviour and tests where applicable. - [ ] `/` (home / landing) - [ ] `/login` - [ ] `/register` - [ ] `/profile` - [ ] `/skills` - [ ] `/experience` - [ ] `/settings` - [ ] `/notes` (the TanStack reference route) - [ ] `/offline` (force-static today; document the Expo equivalent) - [ ] Any 404 / error pages ## Acceptance criteria - [ ] Every existing route from `app/` is reachable in the Expo client. - [ ] Cross-user isolation behaviour (404 on someone else's data) verified end-to-end on at least Skills and Profile. - [ ] No screen reads from `apps/api` source — all data flows through `packages/api-client`. - [ ] Visual parity on both themes. - [ ] i18n: strings load via the new runtime; placeholder text and ARIA labels survive. ## Out of scope - Deleting the Next.js UI files (its own ticket — easier as a single cleanup PR). - New visual designs — this is a port, not a redesign. ## Composes with Expo scaffolding, Decommission Next.js UI. ## Part of #176

james added the

area:pwa

feature

labels

2026-06-20 15:45:24 +00:00

james referenced this issue from a commit

2026-06-20 16:12:23 +00:00

docs(adr): adopt ADR-0027 for frontend/backend split (#177)

james referenced this issue

2026-06-20 16:12:41 +00:00

docs(adr): adopt ADR-0027 for frontend/backend split (#177) #189

james referenced this issue