BandBaajaChaos

A satirical simulator for planning the internet's biggest wedding.

View it live ↗

/At a glance

RoleSolo build
Context10kdesigners sprint
StackReact, Vite, Vercel
Year2026
Landing screen: garland loop and the BBC wordmark on cream

Humans love rehearsing fantasies. We scroll wedding reels, price venues we'll never book, build Pinterest boards for a day that's years away.

Band Baaja Chaos hands you the whole fantasy, the decisions, the drama, the questionable choices, minus the invoice.

/The sprint

72 hours to lock it and ship it

A design sprint with the 10kdesigners community. 72 hours to lock the idea and ship the first version with Claude Code. No backend, no database.

The constraint shaped the product: build only what made it fun, nothing else. And once it was live, it never really stopped moving.

Late-night sprint session, session summary for future Claude

/The design rule

The machine is modern. The content is desi.

A clean editorial interface. Then let all the desi-ness live where it actually lives: in the illustrations, the copy, the sounds, the sheer maximalism of the choices.

Restraint in the frame so the chaos inside hits harder.

Category screen: the calm editorial frame
The landing screen - calm before the chaos begins.

/v1, the weekend build

A wedding has a hundred decisions

Dumping them all on one screen would feel like a spreadsheet.

Tap through cards, theme, venue, guests, food, the big day. Every choice spikes the budget. You know it's absurd. You keep tapping anyway.

The burn cash meter never leaves the screen, climbing into numbers no one should spend on a single day.

Sensory hits along the way: shehnai and dhol when you level up, flower shower raining down.

The bill never leaves the screen.
Palette
Warm cream, coral red, marigold gold
Display
Rozha One
Body
Bricolage Grotesque
Voice
Hinglish from word one, never translated
Stack
React and Vite on Vercel. No backend, no database

Started on Netlify, hit deploy limits, moved to Vercel.

/First response

It landed with the people it was built for

Shared with the 10kdesigners community first. The Hinglish, the specific references, the marigold mayhem. Not everyone got it. That was the point.

It opened up opportunities. Good conversations with designers, people asking how it was made.

Community reactions: WhatsApp or community thread Instagram story replies from people who played it

/Reading the feedback

Shipping v1 wasn't the finish line

Where I'd been unapologetically desi, people leaned in.

The loud, specific, cultural moments landed hardest. Where I'd been generic, eyes glazed. Cultural specificity isn't a risk. It's the whole mechanism.

Users kept suggesting: a burn meter that actually burns, a clearer jump from level one to level two, more moments that felt lived-in. So iteration became constant, each pass making it more simulative, not just more polished.

Watching people play told me more than any note did.

/Turning it up

The energy dropped where it should have peaked

Processing lines, sensory music, the whole build-up. Then just a collectible souvenir and a flower shower. Not as per the feedback, people expected visuals, a beat for every choice they made.

The ticker loop fixed it. Cards running diagonal, infinite, the energy finally not dropping.

Prices floating on every card. Money climbing choice by choice hits different than just a total.

/The voice

A simulator that sounded corporate would have died on contact

The words carried as much as the pixels. Hinglish, never translated, doing the satire, poking at the whole big-fat-wedding machine from the inside. Paid by: vibes. Marigold mayhem.

Launch story: go get your hands dirty, once in a lifetime wedding chaos awaits In-app copy: Level 2 Bandobast, the extras, the excess, the everything
Exactly how it dropped on my IG.

/What I learned

The idea came before the tools

The brief pushed toward virality. It landed on weddings through family chaos at home, real conversations, real energy.

I skipped customization deliberately. Open input invites misuse, and without time to moderate, keeping the authored voice tight was the right call.

The tools made speed possible, but the thinking, the taste, the calls on what stayed and what got cut, that was the work. And creation, once it starts, is infectious.

/Parked for later

Custom theme input and multi-select across categories. Held back to keep the focus on additions that carry weight, not endless ones.