Design and engineering for sharper product systems | Book a intro to start building with our squad.

Back to Work

Wish · 2023 — 2024

Wish — Wishlist Commerce Platform

A social wishlist platform that turns shared intent into checkout — designed for calm discovery and reliable conversion.

  • ClientWish
  • RoleProduct Design & Full-Stack Engineering
  • Timeline2023 — 2024
  • IndustryE-commerce
Hands holding a phone over a soft retail surface

Background

Where the project began

Wish began as a simple idea: let people collect what they want and share those lists with friends and family. Early versions proved demand, but the product felt fragmented — discovery, gifting, and checkout lived in separate mental models. Dawn partnered to unify the experience into one commerce system that still feels social and human.

The problem

What we set out to solve

Users abandoned lists before converting. Merchants lacked clear attribution. The interface asked people to learn too many steps between inspiration and purchase, especially on mobile. The team needed a sharper product story, a calmer IA, and a stack that could scale without slowing iteration.

Approach

How we moved

We mapped the full journey from save → share → gift → buy, then redesigned around a single primary path. Brand and product surfaces were rebuilt on shared tokens. Engineering focused on reliable cart state, notification hooks, and merchant dashboards that explain performance without noise.

Stages of work

The work journey

01/08

Scroll to move through the journey

  1. preparation

    01Brief & Discovery

    Stakeholder interviews, funnel audits, and competitor walks to define what Wish must mean in one sentence.

  2. start

    02Journey Mapping

    Mapped save, share, gift, and buy paths — then cut every screen that did not serve a verb.

  3. explore

    03IA & Sketching

    Wireframed mobile-first structures and tested information hierarchy with real wishlist scenarios.

  4. structure

    04Prototype

    Built clickable flows for list creation, gifting, and checkout to pressure-test edge cases early.

  5. craft

    05Visual System

    Defined type, color, and component tokens so product and marketing stayed one brand.

  6. build

    06Build Components

    Implemented shared UI primitives, cart state, and notification patterns in production code.

  7. finish

    07Client Review

    Presented builds with founders, captured corrections, and locked scope for the launch cut.

  8. launch

    08Ship & Measure

    Released in staged cohorts, instrumented list-to-checkout, and iterated on friction points.

Tech stack

Tools that carried the build

Chosen for reliability, speed of iteration, and fit to the product surface.

  • Next.js
  • Laravel
  • React
  • Figma
  • PostgreSQL
  • Docker

Outcome

What changed after launch

Wish shipped a clearer product narrative, a redesigned mobile-first flow, and an operations layer merchants could trust. Conversion improved, support tickets around list confusion dropped, and the team gained a system they can extend without redesigning from scratch.

  • 2.4×

    List-to-checkout rate

  • 38%

    Faster mobile task time

  • 0 → 1

    Merchant analytics suite

Services

  • Product Strategy
  • UX/UI
  • Engineering