On TwoTickets, you Twoot an event in order to connect with others around that shared plan. The flow is simple: Twoot → Match → Chat → Decide → Go. You don’t see profiles or matches until you Twoot events, so plans come first and profiles second.
The aim is to make meeting new people more natural: the event itself is the ice-breaker, not a random line in a bio. We’re in soft launch now and would love feedback from HN — does this “event-first” approach resonate with you, and where do you see the pitfalls?
Paul Graham once said that all dating apps are really just matching apps. I wonder: how close is this to a solution to that assertion — although TwoTickets is broader than dating.
*Links:* - Website: https://www.twotickets.us - iOS App: https://apps.apple.com/us/app/twotickets-match-eventfully/id...
aammundi•5mo ago
TwoTickets isn’t meant to be “just another dating app.” I see it more as a matching engine for shared experiences. Most platforms match people on profiles — I wanted to see what happens if you flip it and match on plans.
I think of it as Uber...when you open the app, you're thinking about where you want to go and the rest happens automatically. On TwoTickets, it is - "What you want to do"
That shift changes a lot:
The ice-breaker is the event, not a bio.
Plans are time-bound, so conversations don’t drift into dead-ends.
Safety and trust feel higher when there’s clarity on why you’re connecting.
On the tech side: it’s a Django + Celery + Postgres stack with a fair bit of scheduling and clustering and feed generation logic to ingest events and suggest matches. Happy to dive deeper into that if folks are interested.