🚀 MyMealMind — Project Story
💡 Inspiration
As someone who often saves recipes in scattered places—bookmarks, notes, screenshots—I wanted a central, beautiful, and functional place to manage everything. MyMealMind was born from a desire to organize recipes, share creations, and explore a growing cooking community, all while maintaining control over privacy and publishing.
🛠️ How I Built It
- Frontend: Built with modern
React+TypeScript, styled withTailwind CSS, and deployed viaNetlify. - Authentication & Database: Managed by
Supabase, including auth, image storage, and email verification. - Email Domain: Connected a professional domain and mailbox via
IONOS. - Payments & Subscriptions: Integrated
RevenueCat Web SDKwithStripeto handle Pro subscriptions, including a badge system and publication limits. - Serverless Logic: Configured
Supabase Edge Functionsto manage subscription cancellation hooks. - CI/CD & Live Previews: Managed in
Bolt, connected withGitHubfor seamless updates.
📚 What I Learned
- How to implement role-based access control (e.g., guests, free users, Pro users).
- How to use
Supabase SMTPwith a custom domain. - How to handle soft limits for free-tier publishing.
Stripeintegration viaRevenueCatwithout native mobile SDKs.- Building a Pro onboarding flow with a badge, unlock visuals, and gated publishing.
⚠️ Challenges
- Handling delayed email confirmations and the user flow for unverified users.
- Ensuring likes and filters worked without triggering infinite loops in
Reactstate. - Managing route-level access for unpublished or private content.
- Debugging
RevenueCatpurchase validation across subscriptions (monthly/annual). - Making the UI feel premium, intuitive, and still performant.
🌐 Live Site
Built With
- authentication
- bolt
- edgefunctions
- github
- ionos
- netlify
- postgresql
- react
- reactrouter
- revenuecat
- smtp
- storage
- stripe
- supabase
- tailwindcss
- vite



Log in or sign up for Devpost to join the conversation.