Private Client Project

A collaborative planning system for the decisions that usually disappear inside a group chat.

A live-synced event planning workspace that coordinates availability, RSVP, polls, food decisions, gift-exchange planning, deadlines, and organizer oversight across desktop and mobile.

Private event planning becomes operationally complicated long before it begins to look complicated. A few date options, several guest preferences, changing decisions, and a series of reminders can quickly become scattered across texts and informal notes. This product brings those decisions into one structured but still celebratory experience.

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

ProjectCollaborative Private Event Planning Web App
CategoryProduct Design · Front-End Development · Event Technology · Workflow Automation · Data Management
ClientPrivate Client Project
My roleProduct strategy, UX and workflow design, UX writing, visual design direction, front-end implementation, Supabase data architecture planning, responsive testing, Vercel deployment, and iterative product refinement.
TechnologyHTML · CSS · JavaScript · Supabase Postgres · Supabase Realtime · Row Level Security · Vercel · Open Graph metadata · PWA and Home Screen assets
Desktop home screen for a private event planning web app showing Start Here guidance, deadlines, and planning snapshot cards.
A desktop view of the private event planning home screen with onboarding steps, deadlines, and a planning snapshot.

Overview

A warm guest experience with enough structure for the host to make real decisions.

The app centralizes availability, RSVP tracking, polls, food planning, gift-exchange options, and organizer controls within one responsive product. Guests can complete the core planning steps themselves, while the host has a dedicated administrative view for understanding participation and finalizing decisions.

The design needed to feel personal enough for a private celebration without becoming so informal that deadlines, response states, and organizer authority were unclear.

The Challenge

A lightweight private experience still needed a rigorous planning model.

The group did not need a heavy account system or a public RSVP site. It needed a trusted private environment that could keep several interdependent decisions in one place.

The primary challenge was balancing simplicity for casual guests with enough structure for the organizer to monitor participation, compare date options, close polls, and move the group from open discussion to final plans.

  • Keep availability, RSVP, polls, and gift planning connected.
  • Make the main scheduling workflow easy to find on mobile.
  • Prevent participants from changing organizer decisions.
  • Clarify deadlines without making the product feel formal or cold.
  • Protect private event details and participant information.

The Solution

A guest journey and organizer workflow designed as related but distinct experiences.

Guests begin with a lightweight participant profile and password, then move through Availability, RSVP, Polls, Eats & Drinks, and Gift Exchange. The Home screen provides orientation, deadlines, and the current planning state without asking participants to reconstruct the process from prior messages.

The organizer sees a separate operational layer: participation progress, leading dates, incomplete tasks, decision controls, and the ability to lock the final plan when the group has provided enough information.

Designing the Scheduling Workflow

Availability became its own product surface when the calendar proved too important to remain buried.

An earlier structure placed the scheduling workflow inside broader overview content. Testing showed that the most consequential planning task had become difficult to locate, especially on mobile.

I moved Availability into its own tab, paired the calendar with ranked-date visibility, and kept the organizer’s date-lock action close to the evidence supporting the decision.

Availability tab showing a calendar, date ranking, and a lock date button for the organizer workflow.
Dedicated availability workflow with ranked date results and a calendar-style response view.

Product and Workflow Strategy

The app turns planning into a sequence of lightweight, self-service decisions.

01

Home

Introduces the process, deadlines, current planning snapshot, and the participant’s next steps.

02

Availability

Collects date responses, displays ranking, and gives the organizer a clear date-lock workflow.

03

RSVP

Handles attendance, deadline communication, and participation acknowledgment before submission.

04

Polls

Supports group decisions without losing context in parallel text conversations.

05

Eats & Drinks

Holds food sign-ups until the catering-versus-potluck decision is final, preventing premature commitments.

06

Gift Exchange

Explains open options while keeping the final selection under organizer control.

07

Admin

Shows participation, incomplete responses, leading dates, and organizer-only decisions in one operational view.

Mobile home screen for the event planning app with condensed navigation, start steps, and deadline cards.
The mobile home experience preserves the same orientation and deadlines in a narrower composition.
RSVP screen showing attendance options, final RSVP deadline, and a participation notice.
RSVP workflow with a deadline and participation notice before guests submit attendance.

Guest and Organizer Journey

The same data supports two different questions: what should I do next, and what does the group still need?

Participant

  1. 01Select a profile and create a private password.
  2. 02Submit availability before the scheduling deadline.
  3. 03Complete polls and return as decisions evolve.
  4. 04Respond to the final RSVP and review confirmed plans.

Organizer

  1. 01Monitor who has joined and what remains incomplete.
  2. 02Compare ranked dates and poll direction.
  3. 03Lock the final date and decision states.
  4. 04Publish the final planning summary for the group.
Polls and gift exchange screen showing fictional voting results and pending gift-exchange format options.
Polling and gift-exchange states help the group make decisions without losing the reasoning behind them.
Eats and Drinks screen showing paused food sign-ups, host-provided items, guest input, and fictional book drive commitments.
Food sign-ups remain intentionally paused until the group selects a food format.

Administrative Workspace

Organizer control was made visible, then deliberately narrowed.

The Admin dashboard summarizes participation, date direction, open decisions, and individual progress. Administrative access was initially expanded, then reduced after testing showed that broader permissions created unnecessary risk of accidental changes.

The final model ties organizer controls to the host’s own login instead of creating a separate Admin participant profile. Regular guests can understand the planning state without being given the ability to finalize it.

Admin dashboard showing fictional invited profiles, joined users, pending tasks, date lock controls, and progress rows.
Organizer dashboard for reviewing participation, leading dates, unresolved decisions, and individual progress.

Privacy and Data Design

A trusted private environment required clear limits rather than the appearance of enterprise security.

The product uses a fixed private roster and lightweight participant passwords appropriate to a trusted planning group. It is not presented as a high-security identity platform.

Supabase provides shared data storage and realtime synchronization. Browser-exposed configuration is limited to public client values, while privileged service credentials remain outside the front end. Organizer-only controls are separated from participant workflows.

The portfolio version replaces all identifying information with fictional names, generic dates, and non-sensitive planning content.

  • Fixed private participant roster
  • Lightweight personal passwords
  • Organizer-only decision controls
  • Realtime shared responses
  • No service-role credentials in browser code
  • Fully fictional portfolio data

Visual and Interaction Design

Celebratory warmth was treated as atmosphere, not an excuse for operational ambiguity.

Seasonal without visual noise

Burgundy, emerald, cream, gold, rounded cards, gentle depth, and visible snowflakes establish the occasion while preserving readable content surfaces.

Decision states with context

Pending, open, locked, and finalized states explain not only what the current condition is, but why a participant can or cannot act.

Shared-link polish

A custom text-message preview and iPhone Home Screen icon make the entry point feel like part of the product rather than an unformatted URL.

Responsive Design

Mobile was the primary guest context, while desktop remained essential for organizer oversight.

The app was designed to arrive through a text message. Mobile refinements included horizontally scrollable navigation, compact deadline cards, readable action states, a focused Availability tab, and layouts that prevent the planning sequence from disappearing beneath decorative content.

Technical Approach

A static front end with a live shared-data layer.

The application uses HTML, CSS, and JavaScript on Vercel, with Supabase Postgres and Realtime supporting participant profiles, availability, RSVP records, poll votes, food-planning state, gift-exchange state, and organizer controls.

Open Graph metadata, a PWA-style manifest, custom icon assets, cache-busting, and repeatable backup-and-deployment scripts support the production experience and ongoing maintenance.

Iteration and Problem Solving

The product improved when the planning sequence became more explicit.

01

Availability moved into its own tab

The scheduling workflow had become buried inside Home. Separating it made the most important early action immediately visible.

02

Admin access became host-specific

A separate Admin profile and multi-admin model were tested, then removed to reduce accidental changes and simplify the mental model.

03

Food and gift workflows respected decision order

Food sign-ups and exchange assignments remained pending until the group had selected the underlying format.

04

Deadline and participation language moved closer to action

Guests see the relevant notice before responding rather than learning about expectations after submission.

05

The shared link became a designed entry point

Snowflake motion, the social preview, and the iPhone icon were refined as part of the guest experience rather than treated as packaging.

Outcome

A scattered conversation became a complete, live-synced planning product.

The completed application gives participants one destination for availability, RSVP, group decisions, and evolving plans, while giving the organizer an operational view of what has been completed and what still requires a decision.

No attendance, engagement, conversion, revenue, or time-savings metrics are claimed. The verified outcome is the finished product itself: a deployed, responsive, live-synced planning experience with participant workflows, organizer controls, and a privacy-safe portfolio presentation.

Key Takeaways

What the project reinforced.

  • Small private-event workflows benefit from the same information architecture and permission thinking as larger digital products.
  • The order of decisions matters; later workflows should not invite action before earlier choices are settled.
  • Mobile navigation must reflect the guest’s actual task priority rather than the order in which features were built.
  • Organizer authority is easier to trust when it is visible, narrow, and connected to a real role.
  • A warm visual identity and a practical operational model can strengthen each other.

Does your group workflow need more than another message thread?

I design custom digital experiences that turn scattered coordination into clear, usable products.