Revive Happenin
A local events app that discovered the hard part was venue supply, not the feed UI
The opportunity
A general local-events app is too broad for an indie builder. The viable revival is a narrow local media product: one city, one event category, curated deeply enough that users trust it more than social feeds.
What happened
What it was
Happenin was a local events app for my city (Austin). It aggregated events from multiple sources — venue websites, Facebook Events, Eventbrite, Instagram posts from bars and venues — into one feed organized by tonight, this weekend, and this week. Users could filter by type (music, food, comedy, art, outdoors, nightlife), save events, and share them with friends. I also built a 'surprise me' feature that picked a random event for tonight. The idea was to be the definitive 'what's happening' guide that replaced Googling, checking Instagram, and scrolling Facebook Events.
What worked
The UX was good. The 'tonight' feed with category filters was clean and fast. People who used it during SXSW week (when I happened to have good event coverage) said it was the best way to find things to do. The 'surprise me' button was fun and people shared screenshots of random events with friends. A few Austin food bloggers shared the app, which drove my best download days.
Why it failed
I could not keep the event data fresh. This was the fundamental problem and I underestimated it by an order of magnitude. Most local events aren't on Eventbrite or Facebook Events. They're announced on Instagram stories, printed flyers in coffee shops, word of mouth, or venue-specific websites with no structured data. Scraping was fragile and missed most events. I tried building a submission form for venue owners, but getting venues to submit events was a full-time sales job — I'd email 30 venues and get 2 responses. At any given time, my app showed maybe 15-25 events for a city with hundreds happening nightly. Users opened the app, saw a thin list that missed obvious things their friends were going to, and closed it. A sparse events app is worse than no app because it implies nothing is happening.
Key lesson
Treating an event supply problem as a tech problem. I spent 80% of my time building scrapers, aggregation logic, and a nice UI. I spent 20% on actually sourcing events. It should have been the reverse. The tech was the easy part — building a nice feed took 2 weeks. Filling the feed with comprehensive, accurate event data for even one city was an unsolved problem that required manual outreach, partnerships with venues, and a content operation. I was a developer building a product that needed a sales team.
Available assets
Founder intent
App Graveyard has not verified ownership, asset claims, pricing, or availability. This is an interest signal, not a transaction.
What to watch out for
Distribution was the original bottleneck. A revival needs a clear channel to users.
Express revival interest
Interested in reviving Happenin? Submit your interest below. App Graveyard reviews every inquiry before anything is forwarded to the founder. Private contact details are never exposed publicly.
More revival opportunities
TabSnooze
30A lightweight Chrome tab snoozer that worked well but had no distribution engine
ProseAI
40A voice-matching AI writer that grew fast before platform AI made the core feature ordinary
SkillSwap
30A skill-barter marketplace that ran into the double-coincidence problem immediately
Got a dead app with revival interest?
List your app on the Revival Board. Share what you built, what assets remain, and what kind of partner or buyer you're looking for.