Skip to content
All work

Case study · 2026 · Freelance project

Alice Ivy: Cycle-Synced Wellness App

A women's wellness app live on iOS, Android and web, built end to end by a single developer, from cycle tracking to subscription billing.

TodayDay 14Ovulation phaseFocus at workPitch, presentJournaliOSAndroidWebpremium7-day free trialStripeRevenueCatwebhooks → Postgres
Role
Solo full-stack & mobile developer, from first commit to App Store and Play Store release
Stack
ReactTypeScriptViteTailwind CSSCapacitorSupabaseStripeRevenueCatNestJSTanStack QueryResendGeminiRailwayVercel
Website (opens in a new tab)App Store (opens in a new tab)Google Play (opens in a new tab)

Results

01 The problem

Alice Ivy helps women plan their work, energy and self-care around their menstrual cycle: which phase she's in, what to focus on at work, meditations, journaling and AI-generated insights. It had to ship on iOS, Android and the web, with one developer and one subscription that works everywhere.

02 What I built

  • One React + TypeScript codebase shipped to the App Store and Google Play with Capacitor, and to the web.
  • A cross-platform subscription model: Stripe for web, RevenueCat for App Store and Google Play, one shared premium entitlement and a 7-day free trial.
  • A Supabase backend: Postgres with row-level security, auth, storage, scheduled jobs and ~40 edge functions.
  • Cycle-tracking logic (phases, ovulation window, period predictions, adaptive cycle length) reused across the app, notifications and calendar sync.
  • AI features for journal reflections, cycle insights and a wellness companion chat.
  • Personalised notifications (web push, local mobile notifications, transactional email with Resend) and calendar integrations with Google, Apple and an Outlook feed.
  • A separate admin panel (NestJS API + React) for members, subscriptions, payments, promo codes and free access, with two-factor sign-in and a full audit log.

03 Architecture

  1. 01 · Clients

    • React + TypeScript (Vite)
    • Capacitor for iOS and Android
    • Web app on Vercel
  2. 02 · Backend

    • Supabase Postgres + RLS
    • Auth, Storage, scheduled jobs
    • ~40 Edge Functions
  3. 03 · Billing & ops

    • Stripe + RevenueCat webhooks
    • NestJS admin API on Railway
    • Resend email, Web Push

04 Hard parts

One subscription across three stores

Apple and Google require their own in-app purchases, while web users pay through Stripe. I made the database the single source of truth, and Stripe and RevenueCat webhooks keep it in sync through trials, renewals, cancellations, refunds, restores and account transfers.

Safe, retry-proof billing events

Webhook handling is idempotent and retry-safe, with repair jobs that detect and fix drift, and checks so one user's purchase can never be written onto another account.