AEYA Perimenopause Health, App and Backend Done Right
Co-built AEYA as a mobile-first women's health platform for perimenopause — unified symptom tracking, cycle intelligence, clinically responsible content, and a privacy-aware Express + Supabase backend with EN/DE support from day one.
AEYA addresses a systematic gap in women's healthcare: the perimenopause life phase — millions experience it, few products treat it with the emotional and medical context it deserves.
SolutionPlus partnered from the first idea as co-creator — not just implementing tickets, but shaping product concept, functional planning, and delivery across both the mobile app and the backend API that powers tracking, insights, content, and notifications.
Product vision
One platform for perimenopause
Health-tech, education, and community — connected in a product that respects emotional and medical context.
Track & understand
Daily check-in, calendar, and cycle context — symptoms in patterns, not isolation.
Learn & community
CMS-driven content with clinically responsible tone — education that fits the life phase.
Privacy-first platform
EU data residency, in-app export and deletion, consent-aware architecture.
The Challenge
Perimenopause products often fail because they treat symptoms in isolation — without cycle context, without tone-appropriate education, and without infrastructure that meets health-sector privacy expectations. AEYA needed a platform that connects understanding, tracking, and community in one coherent product, not a feature checklist.
- •A life phase with high emotional load — UX must respect medical context, not generic wellness patterns
- •Daily tracking across 22+ symptoms, period, activities, sleep, and notes — with backdating and calendar views
- •Insights that translate entries into Daily Burden Score (DBS), trends, and cycle phase — not raw data dumps
- •Content and commerce (articles, audio/video, affiliate products) integrated without breaking clinical tone
- •Backend that scales notification templates, Gemini-assisted insights, and Webflow CMS — with EU data residency
Our Approach
We mapped the product around how women actually experience perimenopause: check-in first, context second, education third. Architecture decisions — Supabase in the EU, Express domain services, mobile-first navigation — followed that journey. Sensitive content delivery (tone, timing, context) was engineered alongside auth and tracking, not added later.
"Health products carry weight most software does not. Clinical context and user safety are engineering constraints — not design preferences."
Platform flow
From check-in to insight
Mobile app and backend share the same domain model — from daily entries through dashboard, content, and notifications.
Check-in
Symptoms · period · sleep
Insights
Burden score · trends
Content
Webflow · shop
Notify
Push · templates
Audit & scope
MVP shipped, roadmap documented
Cross-repo audit (June 2026): core flows are production-ready — premium, share, and infra hardening stay on a clear post-MVP backlog.
Shipped in MVP
- Auth (email, Google, Apple) + 8-step onboarding
- Unified daily check-in and symptom preferences
- Calendar with cycle phases and backdating
- Dashboard: DBS, trends, streak, cycle context
- Notification engine with templates, push, and preferences
- Content hub + shop via Webflow CMS
- GDPR export and account deletion in-app
- Full EN/DE localization
Documented post-MVP
- Premium subscriptions / RevenueCat backend
- Share and social flows end-to-end
- Legal content APIs or finalized static delivery
- Rate limiting and security hardening
- Consolidate legacy check-in routes
What We Built
Delivery spanned the full stack: consumer mobile experience, API layer, data model, notification engine, and CMS-driven content — one product narrative from onboarding through daily use.
Mobile App (AEYA-app)
Expo-based React Native app with health-sensitive UX, unified check-in, and full EN/DE localization.
Backend API (AEYA-backend)
Express + TypeScript API on Supabase — domain logic for tracking, insights, notifications, and content integrations.
Privacy, Content & Compliance
Health-sector expectations built into data handling and in-product legal surfaces.
What the product gained
AEYA left with a cohesive MVP foundation — not siloed app screens and an API that diverged. The same domain language flows from check-in through insights to notifications.
One journey, two codebases in sync
Mobile flows and backend contracts were shaped together so dashboard cards, calendar phases, and check-in fields reflect the same data model.
Health-sensitive UX by design
Emotional and medical context informed navigation, copy timing, and insight presentation — not bolt-on disclaimers.
Privacy-aware from schema to settings
Export, deletion, and consent-oriented handling were product features, not compliance afterthoughts.
Delivery & Quality
Cross-repo delivery with milestone-based transparency; backend test coverage on critical paths; frontend validated through structured QA on auth, check-in, and dashboard flows.
Co-creation from concept to code
Functional planning and implementation tracked together — scope evolved with product clarity, not change-order friction.
Domain-rich backend
Jest coverage on auth validation, calendar phase logic, dashboard calculations, notifications, and AI payload shaping.
Production-ready MVP scope
Core flows shipped: auth through daily tracking, insights, content, shop UX, and notification infrastructure.
Structured QA on critical paths
Frontend validated through structured manual QA on auth, unified check-in, and dashboard refresh — while backend gained Jest coverage on domain logic.
Clear follow-on queue
Premium subscriptions, share flows, rate limiting, and legal-content APIs documented as post-MVP — without blocking launch paths.
Architecture & Tech Stack
Stack choices prioritized maintainability, health-data sensitivity, and parallel mobile + API delivery — not trend-chasing.
Engagement at a Glance
Product surface
Mobile app + Express API on Supabase (EU)
Symptom tracking
22 symptoms on structured 1–10 scales
Languages
English + German
Core API domains
Auth, tracking, calendar, insights, notifications, content/commerce
Backend tests
Auth, calendar, dashboard, notifications, AI payloads
Compliance tooling
GDPR export + account deletion in-app
Delivery
German-led, milestone-based, defined handovers
Why This Engagement Worked
Healthcare products fail when engineering treats clinical sensitivity as a design preference. We treated it as a constraint from architecture through copy timing — and stayed co-creators from the first idea through implementation.
True Co-Creator, Not Ticket Factory
We invested in understanding the product core before locking scope — conceptualization and functional planning shaped what got built.
Full-Stack Ownership
Mobile and backend evolved together; no handoff gap between “app team” and “API team.”
Privacy & Tone as Engineering
Data architecture and content delivery patterns matched health-sector expectations from day one.
German-Led Delivery Discipline
Clear milestones, visible progress, and accountable handovers — without vendor lock-in on IP.
What Made This Different
Generic wellness UI applied to a hormonally complex life phase
UX engineered around emotional and medical context — check-in, cycle, insights
Mobile app built first; API retrofitted to match screens
Shared domain model across React Native client and Express services from planning
Content and tracking as separate products with inconsistent tone
Webflow CMS + in-app resources with clinically responsible delivery patterns
Privacy policies only; no export/delete in product
GDPR tooling wired through backend and exposed in settings
Static notification copy with no insight pipeline
Template engine + Gemini-assisted generation with cron scheduling on Supabase data
Expo · React Native · TypeScript · React Navigation · Node.js · Express · Supabase · Gemini · Webflow · Expo Push · i18next · TanStack Query · MMKV
Product discovery, mobile development, backend API engineering, Supabase data modeling, notification systems, CMS integration, QA, privacy-by-design guidance
"Perimenopause health deserves products built with clinical sensitivity, privacy-aware architecture, and co-creation — not generic wellness wrappers."
"When developing our app, it was vital for us to find a true partner from the very first idea. Instead of just blindly following requirements, they took the time to truly understand the core of our product. They supported us as a true co-creator throughout the conceptualization, functional planning, and final implementation. Thanks to their holistic guidance, the app turned out exactly as we envisioned it, a true win for our collaboration."
AEYA
Get in touch
Ready for similar results?
Let's talk about how we can turn your challenges into success stories.
German-led delivery
Clear ownership and senior engineering — never blackbox outsourcing.
EU & US timezone overlap
Daily overlap with teams in Germany and the US — synchronous when it matters.
From MVP to scale-up
One partner across AI, web, mobile, and UX — through every stage of your product.
Email us
admin@solutionplus.io
Response time
Within one business day