Hormone therapy management that never phones home
The problem
Trans health apps ask people to hand their medical transition to a server and their identity to a login form. The safety requirements here are not a feature list. They decide the architecture.
What we built
Dose schedules, site rotation, refill windows, and appointment logic live in a shared core with its own tests, and both the web app and the mobile app consume it. Neither platform owns the rules.
The web target runs Tailwind v4 and the mobile target runs Tailwind v3 through NativeWind. A design-token pipeline compiles one source of truth into both, so the brand cannot drift between platforms.
Storage is local-first with optional device-keyed sync and no account. The application works fully with no database and no API key, degrading to a demo responder instead of an error page.
An app-wide quick exit leaves for a neutral site from any screen. Onboarding asks for a chosen name and pronouns, treats every field as optional, and the AI carries both into its system prompt alongside a medical-advice guardrail.
Chat responses retrieve from a curated corpus of real organizations and render inline numbered citations as source cards, so a claim about hormone therapy always shows where it came from.
What this demonstrates
Universal applications where safety, privacy, and citation are architectural constraints, not settings a user has to find.
Get in touch
Tell us what you are trying to build and what is in the way. We will tell you early if we are not the right fit.