Every page uses the same soft surfaces, restrained hierarchy, and lower-pressure interaction model.
About amparo.ai
A quiet interface for calmer AI conversations.
The prototype is intentionally simple: static pages, shared styles, and local state. That simplicity makes it easy to wire real room logic, billing, history, and user accounts incrementally without redesigning the whole product.
The repo now covers landing, onboarding, video, pricing, history, replay, settings, about, and 404 routes.
Local hooks exist for sessions, plan selection, replay notes, and account preferences so APIs can replace them later.
Design principles
What stays true across the product
- Reduce visual pressure before adding more explanatory UI.
- Let one page hand off naturally to the next instead of making each route feel isolated.
- Keep real product states visible, even in a static prototype.
- Preserve the original design language rather than introducing a new aesthetic layer.
Page map
How the routes are meant to work together
Introduce the room, promise the tone, and push new users to onboarding.
Set intention and defaults before creating the next session record.
Convert the room into takeaways, transcript, and reflection notes.
Persist account and session defaults so the flow feels continuous.
FAQ
What this prototype is and is not
It is production-leaning static frontend code, but the room, billing, and auth layers are still local placeholders.
Yes. It is a static site with shared JS and CSS, plus a lightweight local server option.
Separate entry points make it easier to port each route into whatever backend or frontend stack you choose next.
Local storage makes the flow demonstrable end to end before API endpoints exist.
Explore the build
Walk the product like a user, then replace each local hook with the real one.
If you want the fastest audit path, start with onboarding, then go to video, replay, history, settings, pricing, and finally the 404 page.