Building Ocean Drop: A Wellness App With Soul

Most apps are designed to capture attention. To hook you, keep you scrolling, keep you tapping. The metrics that drive product decisions are retention, engagement, time-on-screen.

Ocean Drop started with a different question: What if an app could help people feel more connected — to themselves and to each other?

The Origin

The idea came from a simple observation. Couples struggle to stay in sync. Not because they don't care, but because modern life makes it hard to pay attention to the subtle rhythms that affect how we feel, how we communicate, and how we show up for each other.

Cycle awareness isn't just a health feature — it's a lens for understanding energy, mood, and connection. When both partners understand these rhythms, something shifts. Conversations become easier. Empathy becomes more natural. The relationship breathes.

The Tech Stack

I built Ocean Drop with React Native and Expo for the cross-platform frontend, Supabase for authentication, database, and edge functions, and an AI chat layer powered by OpenRouter for personalized daily insights. I wrote about the full breakdown in The Stack I Use to Build Apps Solo.

The architecture reflects the philosophy: keep it simple, make it fast, and never let the technology get in the way of the human experience.

Lessons So Far

Three things I've learned building this:

1. Design for meaning, not metrics. When your north star is "did this help someone feel more connected today?" — every product decision becomes clearer.

2. AI should amplify human insight, not replace it. The daily plan feature uses AI to synthesize cycle data, mood patterns, and relationship context into gentle guidance. It's not telling you what to do — it's reflecting back what you might already know but haven't noticed.

3. Ship before you're ready. Perfectionism is the enemy of something like this. The app is imperfect. But it's real, and real people are using it to have better conversations with their partners.

There's something alchemical about this kind of building — transmuting intention into something people can hold. The code isn't just functional. It carries the values you write into it.

The Two-Sided Architecture

One of the hardest challenges was designing for two people who need fundamentally different things from the same data. She needs control and privacy. He needs context and understanding. I wrote a deep dive into the consent flows, RLS policies, per-entry privacy toggles, and gender-aware notifications that make this work in Designing a Cycle-Tracking App That Respects Both Partners.

What's Next

Gamification. Partner sync improvements. A redesigned calendar. And eventually, the kind of features I can't talk about yet because they don't exist anywhere.

The work continues.

---

Want the Full Workflow?

This is one piece of the system I used to ship Ocean Drop in 7 days.

The full playbook has the exact prompts, the pre-build checklist, the security audit workflow — all personalized for your stack via a single Day 0 prompt.

Get the Playbook — $17 →