hangout-planner

Overview

I built hangout-planner, formerly Event Scheduler, to solve a very ordinary coordination problem: casual planning gets scattered across group messages. The app gives people a shared link where they can mark availability, answer follow-up questions, add notes, and view group-facing results.

The project is intentionally lightweight. Participants do not need accounts; the planning flow is centred on a link that can be shared with the group.

What I Built

The main event flow supports availability voting across days. An event creator can create a scheduling or polling link, share it, and collect participant responses.

The app also supports poll-only follow-up questions, participant notes, response text, and an analytics/results view that summarises availability and question responses. That makes the tool useful for more than dates: it can help decide options, preferences, or loose plans around an event.

Data Model

The app keeps the browser experience lightweight while Supabase stores event, question, vote, note, and participant-response data.

I kept the release boundary deliberate: the built app stays separate from source files, configuration, and private project material.

Current State

This project has a real public deployment and a clear practical use case, but it is less backend-heavy than the other featured work. Its stronger points are the no-login planning flow, the Supabase-backed data model, and the clear public release boundary rather than pretending it is a complex backend system.

That still matters. Planning tools tend to look simple, but the data model has to stay clear enough that participant responses, notes, and results can be trusted.

Next Pass

The next useful media pass should capture the planning page, creation flow, participant response screen, analytics/results view, and mobile layout.