<aside> 🎂

Birthday Club helps people remember the people they love, then act thoughtfully when a birthday approaches. The experience spans a calendar, SMS, email, personal messages, shopping, and the gift itself.

This handover is for the human UX/UI team completing the experience. Owner: Daniel Groch. Prepared 11 September 2026, Australia/Melbourne.

</aside>

Open the application · Current source snapshot · Existing shopping brief

Quick reference: 01 · Screen guide & live walkthrough · 02 · SMS, email & off-site journeys · 03 · Shopping brief & design decisions

Read this first

The team’s task is to make the service coherent, clear, and easy to use across every touchpoint. Notifications are core product screens in another medium: their timing, wording, links, and follow-up states belong in the design work.

The member should understand four things: whose birthday is approaching; when it is; what they can do; and what has actually happened after they act. Gifting, writing a personal message, and choosing to skip are all valid outcomes.

The largest unfinished interaction is shopping. Daniel’s direction is a page of collection carousels: up/down to move between collections; left/right to explore products within a collection. Selecting a product leads to a focused confirmation step. Rapid, confident selection is the design objective; comparative speed has not been measured.

How to read the evidence

Label What it means
Observed live Inspected on birthdays.figandbloom.com during this review, including desktop and a 390px mobile viewport.
Configured / source reviewed Verified in the current application code or the inspected live Klaviyo flow/template. This does not prove delivery to a real inbox, a successful payment, or every production state.
Intended Daniel’s stated direction or a documented design requirement. It may still need implementation or a final design decision.
Design reference The existing September 7 prototype. It uses fictional people and simulated states. It is not a screenshot of the deployed application.

The signed-in live walkthrough covered the calendar, birthday entry and its unsaved review, person profile, gift selection/confirmation, birthday-message composer, and account settings. Public entry, authentication completion, guest token journeys, payment completion, and actual SMS/email delivery were reviewed from sources where available; they were not exercised end to end in production. Current live account information and usable recipient/claim links are excluded from this handover.

Who the experience serves

Person Their goal What a good experience feels like
New visitor Get important birthdays out of their head and into a dependable service. “I can start quickly, understand the reminders, and stay in control of spending.”
Returning member / gift sender Act on a reminder, choose well, and know the birthday is handled. “I know who this is for, what happens next, and what I am paying.”
Person answering a request Share a birthday, address, or preferences with someone they know. “I understand who asked and can finish without creating an account.”
Gift recipient / invitee Understand the welcome benefit and decide whether to start their own calendar. “The gift makes sense, the conditions are clear, and joining is my choice.”

The service at a glance

flowchart TD
  A["Discover Birthday Club or follow an invite"] --> B["Build and review a birthday list"]
  B --> C["Choose reminder channel and verify mobile"]
  C --> D["Saved calendar + confirmation SMS"]
  D --> E["Birthday approaching: SMS and/or email"]
  E --> F["Open the relevant birthday in the web app"]
  F --> G["Choose a gift"]
  F --> H["Prepare a personal message"]
  F --> I["Skip this birthday year"]
  G --> J["Review product, address, note and total"]
  J --> K["Shopify checkout and payment"]
  K --> L["Confirmation + gift delivery"]
  H --> M["Member sends through their own app"]
  I --> N["Date retained for next year"]
  L --> N
  M --> N
  N --> E
  L --> O["Eligible recipient finds a welcome card"]
  O --> B

The gift path above shows today’s broad sequence. The intended additional shopping screen sits between “Choose a gift” and “Review product…” The detailed shopping page explains this change.

Primary journeys

1. “Help me remember everyone”

A visitor arrives from the public page or an invitation, adds names and dates, corrects the parsed list, and can leave a date unknown. At save time they verify a mobile number and establish a reminder channel. The calendar and save-confirmation SMS close the loop. A returning member adds more people through the shorter signed-in flow.

Design focus: progress without pressure, clear save feedback, recoverable mistakes, and a precise distinction between “person saved” and “birthday ready for reminders.”