The record of the public profile page redesign (the surface visitors land on at ambasdr.com/{handle}) across web and the mobile app. This is the durable track log; detailed working plans lived in the local dev workflow and are not committed to the repo. Authoritative code lives under frontend/src/components/public/ and mobile/; design rationale lives in docs/DECISIONS.md.
The redesign was delivered in three coordinated workstreams:
Rebuilt the web public page: full-bleed hero portrait, name and role tagline, social row, Chat / Highlights / Files / Links tabs, suggested-prompt cards, and a chat composer with an inline mic that starts a voice session. The old 730-line page was decomposed into focused presentational components orchestrated by a slim container, with a distinct centered desktop layout.
Gave a signed-in owner an in-app way to preview their live public profile: a modal route loads the real redesigned web page in a WebView, pinned to the profile origin (off-origin links open in the system browser), with loading, error, and retry states.
Brought the native mobile public-page surfaces to visual parity with the web redesign: full-bleed hero, centered identity, and a Chat / Links / Files tab model (retiring the old biography tab).
The chat body is a fixed-height reading window rather than a section that grows with the conversation. Messages scroll inside it and fade out at the top edge; short conversations rest at the bottom above the composer and grow upward. The view auto-pins to the newest turn while the reader is at the bottom, and a visitor can scroll up to re-read history. Suggested prompts render as right-aligned chat bubbles, and the voice "listening" state mirrors the desktop stage.
Suggested prompts are backend-driven: the page renders whatever the backend supplies and shows no prompt cards when the field is absent — the product deliberately does not ship curated stand-in prompts for a missing API field. Owner-editable, backend-powered prompts are tracked as a follow-up.
The hero carries an "Add contact" affordance that downloads the owner's vCard, shown only when the owner has exposed contact details. It links to the backend vCard endpoint and lands the visitor in their device's native add-contact screen. The backend contact fields, capture, and endpoint are owned separately (backend workstream); the web button and its gating are part of this redesign.
frontend/src/components/public/ (with Storybook stories and tests).mobile/components/publicpage/, mobile/components/preview/, and the profile-preview route.docs/DECISIONS.md and the design specs under docs/superpowers/specs/.