InviteBunny 🐰 – Animated RSVP Invitation Builder

email: test.enravaled@gmail.com
password: 12345678

🧠 Inspiration

While helping a friend plan their wedding, I realized how underwhelming digital invitations still are — static designs, sending pdfs, and zero interactivity. I wanted to create something better: an easy-to-use tool that lets anyone craft beautiful, animated, and personalized RSVP invitations with tracking built in. The idea was to bring life and elegance to digital invites — something that feels delightful, modern, and event-worthy.

⚒️ How I Built It

I built InviteBunny as a modern SaaS app using:

React + Tailwind CSS + Shadcn UI for the frontend
TanStack Router and TanStack Query for routing and data fetching
Supabase for authentication, PostgreSQL database, and real-time updates
GSAP for smooth invitation animations
Bolt.new AI app builder to accelerate logic and UI workflows without writing backend code manually

Key features include:

Multi-step invite builder for hosts
Theme customization (font, background, colors, animations)
RSVP form with custom fields
Public invitation page with live animation
RSVP tracking dashboard with export functionality

🧩 Architecture Overview

User signs up and is assigned a free plan (1 event, 20 responses)
Invitations are created via a multi-step builder
Each invite has a public link with animated UI
Invitees respond via custom forms, stored in Supabase
Host dashboard displays analytics and response tracking

💡 What I Learned

How to combine Supabase and React to build a real-world SaaS product without a dedicated backend
Structuring an app around a multi-tenant use case with tiered pricing and dynamic content
Handling real-time form rendering based on dynamic schema with auth and role-based permissions
Designing animations with performance in mind using GSAP
Managing MVP constraints with manual payment flows while keeping the UX smooth

🔥 Challenges Faced

Designing a theme editor that supports custom fonts, color pickers, and background search via Pexels API — all without backend support
Enforcing usage limits (like number of events or RSVPs) client-side while maintaining security
Handling manual upgrades for paid tiers due to restrictions on integrating a payment gateway
Balancing the build time for polish vs MVP delivery under tight constraints