Dev notes, product thinking, and honest writing from the team behind Happening.
Happening v1 shipped last month. This post is the retrospective I wish more product teams would publish: the bits that worked, the bits that didn't, and the things I'd do differently if I were starting again tomorrow.
The fastest way to lose someone's trust is to be vague about their data. So this post is the opposite of vague: it is a complete walkthrough of what Happening stores, where it lives, who can see it, and the things we deliberately chose not to do.
On the surface, Happening looks simple. Friends tap the dates they can make, the app surfaces the best date, the host picks. But the moment you start writing the algorithm down, you realise it isn't simple at all.
I went back through my messages last week and counted. Organising one Saturday dinner with six friends had taken 73 messages over four days. Nothing was booked at the end of it.
A few years ago I sat in a group chat with my oldest friends, all of us doctors, trying to pick a date for a party. After 45 minutes of back and forth we gave up. Not one date worked for everyone in the next four months. That was the evening I started thinking about Happening.