Card Ritual: Solo Full-Stack Build

A solo-built tarot journaling web app, three months from concept to launch, grown from nine years of personal daily practice.

B2C Subscription SaaS 0 to 1 Product Strategy UX/UI Full-Stack Development Brand
Role Founder, sole designer and engineer
Team Solo
Timeline 3 months, concept to launch

9 years

of personal daily tarot practice as the research foundation

3 months

from first brainstorm to launch

Solo

designer, engineer, and founder, from brand to back end

Card Ritual app screen showing the daily tarot card pull, the emotional entry point of the product

The Problem

I’ve pulled one card a day for nine years, using a physical journal. That practice is genuinely valuable, but it doesn’t scale the way a memory does. I couldn’t easily look back and see a pattern, a shift, how a reading from three years ago connected to something happening now. Doing that meant flipping through hundreds of handwritten pages. I also just wanted the practice to go where I go, pull a card and log it from my phone, in bed, privately, without needing my physical deck or journal on hand.

The tarot app market isn’t small, it’s a $5.6 billion space with roughly 5 million users globally. But it’s saturated with apps built by people who don’t actually practice. Most either lean fully into mystical, algorithm-generated interpretations, or they’re generic journaling tools with a card deck bolted on. None of them were built by someone with a real, sustained daily practice, and it showed.

The Build

Month one was concept and infrastructure: brainstorming the product with Claude, designing the brand, defining the ideal customer and business model, then building the first versions, a React Native mobile app, a Next.js web app, and an Astro marketing site, all at once. Month two was testing and go-to-market groundwork, user testing with ten different types of users, early email and social strategy. Month three was the hard turn: submitted to the App Store and Google Play, got rejected, rebuilt the payment integration from RevenueCat to Stripe, and made the call to go web-only. That same month is when the smaller delight details went in, theme switching, gesture interactions, onboarding walkthroughs.

Card Ritual's daily loop screen showing a pulled tarot card alongside the journal reflection prompt

Most of the stack was new to me going in, Claude Code, Vercel, even basic SQL. I’d never submitted an app to a store before either. What made it possible was a decade of front-end experience underneath all of it, enough foundation to move fast through genuinely unfamiliar territory.

Apple rejected the app on submission, not for a bug or a policy violation, but because they were actively rejecting tarot and astrology apps outright to reduce category bloat in a saturated space. That’s not a problem you fix with a better app. I changed course entirely, dropped the native app plan, and rebuilt the payment layer for a standalone web app instead. It ended up being the right call. No app store gatekeeping, no 30% cut, full control over the experience.

Where It Landed

Card Ritual launched with a small, real user base, 9 people including me, with 3 to 4 daily journal entries happening consistently. It had paying subscribers at $5 a month. Those were small numbers by design, the focus was proving the product works end to end before pushing on growth. I have since shut the product down.

Card Ritual's entry history view showing past tarot journal entries over time
Card Ritual marketing site and brand identity

What I'd Do Differently

The biggest lesson wasn’t about the build. Tarot people are analog people. They want to sit across from a reader in a room that feels right, watch real cards hit the table, and feel someone there with them. A screen is the wrong medium for that, and no amount of polish fixes it. I pulled my own card in a paper journal for nine years. That should have told me something.

I’d test that before writing any code. A few conversations with people who actually pay for readings would have shown me in a week what the app took months to show me. Most of them want a reading or a meaning from someone they trust, not a tool for building their own intuition. I built for a niche of a niche.

I’d also check the App Store’s stance on tarot apps before committing to a native build. Apple was rejecting the whole category, and I lost weeks building for it.

I shut the app down. The practice goes where the people are, readings and stories in person and on Substack.