01 / The problem
For years, planning a festival with friends meant texting during sets to figure out who was seeing what. And I could never answer simple questions, like when I last saw a band or how many shows I'd been to this year.
02 / Who it's for
People who go to a lot of shows, and the friends they go to festivals with. Most people use it to log concerts. The festival planning is for crews heading to the same weekend.
03 / Positioning
Plan it with your crew. Keep it forever.
Plenty of apps log shows, and a few help you plan a festival. Doors @ connects the two: the sets you plan with your crew land in your show history on their own.
04 / What I built
- One-line loggingType “Green Day @ Moody Center” like a text. It fills in the artist, venue and date, even offline.
- Crew planningA stage-by-stage festival grid that shows which sets your friends picked.
- Save DayYour festival day as a lock screen, with the schedule and map saved for when there's no signal.
- Recap and posterYour year by the numbers, turned into a gig poster you can share.
- An admin consoleWhere I load each festival's lineup, set times and map myself.
05 / How I launched it
I made a feature deck to recruit friends as testers, and a field guide to show them how it works. I ran a public TestFlight with notes on what to test in each build, wrote an App Store listing with six one-line screenshots, and got mod approval to post in r/aclfestival ahead of ACL weekend two.
Testers shaped it. Crew initials on the grid, long-press set details, stages in poster order and the date on Save Day all came from beta feedback.
06 / What I learned
Building it was the easy part. Getting it in front of festival crews is the real work, and every festival has to be loaded before I can promote it. Next up is more of the 2027 calendar, starting with the festivals people request in the app.