08 / 09PRODUCT · WEB
Plan the hang, not the group chat
Group plans often collapse between 'we should hang' and choosing a time, activity and final headcount. Hangs gives one person a short setup flow, then lets everyone else respond through a shared link without an account wall.
I designed the product around progressive commitment: set the constraints once, collect availability and real activity preferences, then turn the group response into a plan people can act on. The interface stays deliberately light so coordination does not become another task.
A live, actively developed product with working creator and guest flows, recurring crews, calendar support, polls, comments, bring lists, expenses, transport and recaps. The case study focuses on the core planning loop rather than listing every feature as proof.
The product decomposes the awkward social work of organising friends into three clear steps: start the hang, let everyone answer once, then lock the strongest plan.
Templates make the first decision small enough to start. A creator can choose the kind of hang quickly or build from scratch, while the rest of the workflow stays available for more complicated plans.
Persistent crews, recurrence, calendar export, notifications, bring lists, comments, expenses, photos, transport and recaps extend the core loop without changing its premise: one shared place should replace the coordination spread across a group chat.
Product strategy, Product design, Responsive full-stack build, Planning workflow, MCP integration
Next.js, React, TypeScript, Turso / libSQL, Tailwind CSS, Framer Motion
Designed and built independently. The interface captures shown here come from the current August 2026 product rather than the retired May version.
