Personal Project

A private planning hub for a girls’ weekend getaway.

A password-protected group planning app that replaces scattered group texts and spreadsheets with one calm, shareable space—built end-to-end for a close friend celebration and designed to be reused for the next one.

Guests log in with a personal password, vote on dates and activities, weigh in on group decisions, submit dietary and RSVP details, and see a live snapshot of where the plan stands—all inside one private, installable app.

Identifying details, project information, and user data have been modified to protect client privacy.

ProjectA Private Planning Hub for a Girls’ Weekend Getaway
CategoryEvent Technology · Product Design · Front-End Development
ClientPersonal Project
My roleProduct strategy, UX and workflow design, UX writing, visual design, front-end development, database architecture, deployment automation, and ongoing product iteration.
TechnologyVanilla JavaScript (ES modules) · HTML5 · CSS3 · Supabase PostgreSQL · RPC functions · Row Level Security · pgcrypto · Vercel · Progressive Web App
Phone-frame screenshot of the Galentine's-style planning app Home screen, showing a welcome card with a numbered planning checklist and fictional progress statuses.
The Home view welcomes each guest with clear next steps—availability, polls, activities, and RSVP—so everyone always knows where planning stands.

Overview

One shared home base for the decisions that usually disappear inside a group chat.

Every friend group that has ever tried to plan a weekend away knows the problem: the group chat fills up with polls, half-answered questions, and “wait, what did we decide?” messages until nobody can find the actual plan anymore. For a multi-day celebration with a guest list, a shared budget, food preferences, activity choices, and travel logistics to track, that chaos gets expensive fast—not in dollars, but in the mental overhead of holding it all together.

This project is a private, guest-managed planning application built to solve that problem for a real friend group getaway. Instead of a public event platform, it is a small, purpose-built tool that only the group can access.

The app was designed, built, and deployed independently, then structured so the same system can be quietly reused as the template for a future gathering without starting from scratch.

The Challenge

Planning broke down in predictable places.

Decisions were buried in chat threads, availability was difficult to update, food and accessibility needs could be missed until the last minute, and there was no single place anyone could check to see where things actually stood.

The experience needed to feel less like a form and more like a shared home base—something the group would actually want to open, while protecting details that were never meant for public view.

The Solution

A focused planning journey for guests and a clear operational view for the host.

The result is a private, installable app with a personal login for every guest, a tabbed workspace covering availability, group polls, food, activities, and final RSVP, plus a live-updating snapshot that turns individual responses into a shared group picture.

A dedicated admin workspace lets the host manage the guest list, adjust poll options, and review responses without reconstructing the plan from old messages.

My Role

A solo build from concept to launch.

I owned this project end-to-end: product strategy, UX and workflow design, UX writing, visual design, front-end development, database architecture, and deployment. I scoped what the tool needed to do, designed every screen and interaction, wrote all guest-facing copy, built the front end and backend integration, set up the private database and access model, and deployed and maintained the live app.

There was no external design, engineering, or backend team involved.

Product & Workflow Strategy

The navigation follows the order in which the group actually makes decisions.

The tool was scoped around a real sequence: first, find overlapping availability; then decide the shape of the trip; then work through food, activities, and transportation; then collect a final commitment.

Reusability was a deliberate constraint from the start. Poll structures, activity options, and guest management were designed so the same system could be reconfigured for a future gathering instead of becoming a one-time build.

Key Capabilities

Each feature maps to a real planning bottleneck.

01

Private guest access

Every guest is added by the host and logs in with an individually assigned password. There is no public sign-up, account-creation friction, or public discovery.

02

Live planning snapshot

A shared Home view summarizes where the group stands across availability, polls, and RSVPs without anyone manually tallying responses.

03

Availability and date voting

Guests weigh in on candidate dates, with a live ranking that surfaces the option with the strongest group overlap.

04

Structured group decisions

Polls cover the overall plan, setting, budget comfort, food style, attire, and transportation so choices do not remain scattered across messages.

05

Activities, food, and RSVP logistics

Activity voting, dietary needs, shared-cost confirmations, accessibility, transportation, and notes to the host remain connected through the same experience.

Phone-frame screenshot of the availability voting screen showing fictional candidate weekends with Yes, Maybe, and No selections.
Guests mark Yes, Maybe, or No against each candidate weekend, giving the host a clean picture of the group’s strongest options.
Phone-frame screenshot of the group polls screen showing selected poll options with fictional guest responses.
Structured group polls turn setting, budget, food style, attire, and more into a clear group choice instead of a scattered thread.
Phone-frame screenshot of the Eats & Drinks screen showing fictional dietary notes and group food-planning responses.
A dedicated space for dietary needs, food preferences, and shared-cost confirmations keeps meal planning from getting lost in the broader conversation.
Phone-frame screenshot of the activities voting screen showing a grid of fictional activity options with vote counts.
Guests vote on activity ideas and can suggest their own, with live vote counts showing which options are gaining traction.

User Journey & Operational Workflow

A guest can move through the plan at her own pace without losing the sequence.

The experience begins with a private link and personal login. Guests land on the planning snapshot, then work through availability, group polls, activities, food preferences, and the final RSVP as the event moves from possibility to commitment.

  1. 01Private login
  2. 02Availability
  3. 03Shared decisions
  4. 04Final RSVP

On the host side, the workflow is equally deliberate: manage the guest list, adjust polls and activities as planning evolves, and review group responses in one place.

Phone-frame screenshot of the final RSVP form showing fictional attendance, dietary, accessibility, and transportation fields.
A closing RSVP captures the practical details a host actually needs: attendance, dietary and accessibility needs, transportation, and a note for the host.
Phone-frame screenshot of the private host admin workspace showing fictional response statistics and a fictional guest list with completion statuses.
A private, admin-only workspace gives the host response stats at a glance and full control of the guest list in one place.

Host Admin Workspace

Guest simplicity is supported by an operational layer the host can trust.

The host can add and manage guests, adjust poll questions and activity options, and review responses across availability, food, activities, and RSVPs.

The planning snapshot answers the host’s most common question—“where do things stand?”—without requiring a manual spreadsheet or a search through the chat history.

Privacy, Security & Data

Private information required a deliberate access model.

There is no public sign-up. Every guest is individually added by the host, guest passwords are hashed rather than stored in plain text, and sessions expire after a defined period.

All reads and writes go through defined backend functions rather than direct, open table access. The underlying database structure and contents are not exposed to the client through unrestricted queries.

The project’s real backend URL, publishable key, live application address, and administrative address are not included anywhere in this case study.

  • Private host-managed guest list
  • Hashed guest passwords
  • Backend-function-only data access
  • Time-limited guest sessions
  • No public case-study link to the app
  • Fictional portfolio names and event details

Visual & Interaction Design

Warm and celebratory without becoming a generic party app.

The visual identity uses deep berry and rose tones, cream backgrounds, and warm gold accents, with a serif display face for headlines and a clean sans-serif for functional content.

Interaction patterns prioritize clarity: selected options use a consistent filled-pill state, group responses remain readable rather than dense, and lightweight stat cards communicate status without asking guests to interpret raw tables.

Responsive & Cross-Platform Design

Mobile-first because real usage happens in spare moments.

Layouts, typography, and tap targets were tuned for a comfortable phone experience, then scaled up for the host’s desktop review sessions.

As a Progressive Web App, it can be installed directly to a phone’s Home Screen and opened with an app-like icon and full-screen launch experience—without an app-store download.

Phone-frame screenshot of the private guest login screen, showing a fictional guest-name selector and password field.
Every guest enters through a private, invite-only screen with an individual password—no public sign-up or searchable listing.

Private, Guest-Managed Access

A welcoming entrance with clear privacy boundaries.

The host controls the guest list, and each invited person receives a personal password. The login experience stays simple for the group while avoiding public registration, searchable profiles, and unnecessary account setup.

Under the surface, guest passwords are hashed with pgcrypto and all reads and writes pass through defined Supabase PostgreSQL functions rather than unrestricted table access.

The front end uses vanilla JavaScript with ES modules, HTML, and CSS, is deployed on Vercel, and includes a manifest and custom icons for installable Progressive Web App delivery.

Iteration & Problem Solving

The discipline was deciding what not to build.

01

Scoped around the group’s actual planning sequence

Each tab maps to a real bottleneck the group had encountered before, rather than a generic event-platform feature checklist.

02

Used backend functions instead of open table access

The RPC-only access pattern required more structure up front but created clearer boundaries around the group’s private data.

03

Previewed locally before every deployment

Changes were reviewed in a local environment before reaching the live, in-use app, reducing the risk of disrupting guests mid-planning.

04

Designed for the next gathering, not only the first one

Guest management, polls, and activity systems can be reconfigured without rebuilding the product from scratch.

Outcome

A private, working planning tool covering the full journey from availability to final RSVP.

The application replaced the group’s prior pattern of scattered chat-based planning with one structured, privacy-respecting home base. It was deliberately engineered for reuse so the system can support a future gathering rather than becoming a disposable one-time build.

Specific engagement, adoption, and satisfaction figures are not published here in keeping with the private nature of the project.

Key Takeaways

What this project reinforced.

  • Small, well-scoped tools can outperform general-purpose platforms when they follow a specific group’s real workflow.
  • Privacy and access control can remain core product requirements even in a lightweight, solo-built application.
  • The order of decisions matters; navigation can gently move a group from possibility toward resolution.
  • Designing for reuse from day one creates direct value the next time the same need appears.
  • A celebratory visual identity can coexist with clear operational structure.

Purpose-built, not generic

Interested in a private tool scoped around how your team, organization, or event actually works?