Rinah Seo

01 / PRODUCT FIRST

Bluprint

A collaborative travel planner that helps people build trips manually, get help from AI, or start from someone else’s itinerary.

Built from 0→1 with a developer, Bluprint brings trip planning, shared itineraries, expenses, and AI-assisted planning into one mobile experience.

ROLE
Product Designer
TEAM
1 Product Designer + 1 Developer
DURATION
Mar 2026 – Oct 2026
PLATFORM
Mobile app
FOCUS
Product strategy · UX/UI · AI experience Developer collaboration
Bluprint Home screen

02 / RESEARCH

Designing beyond my own planning style.

Bluprint began as a small planner I built with Lovable for my own Oahu trip. Since that first version reflected my personal habits, I interviewed 16 travelers to understand how others planned before expanding it into a product designed for other travelers.

16 PARTICIPANTS · AGES 20–40 · 2+ INTERSTATE / INTERNATIONAL TRIPS

KEY FINDINGS

  • Hard to access without a signal

    Some interviewees said they had trouble opening their planner when cellular service or Wi-Fi was unreliable during a trip.

    DESIGN RESPONSE

    We made trip plans available offline so users could still open their itinerary without an internet connection.

  • Limited value after the trip

    Most interviewees treated the planner as a tool for the trip itself and rarely reopened it afterward. A few revisited it to look back on the trip, but there was little ongoing use.

    DESIGN RESPONSE

    We explored two ways to extend value after a trip: Publish, Discover, and Copy turned completed itineraries into reusable plans for other travelers, while Travel Book gave users a way to revisit their trip as a visual recap.

  • Collaboration mattered

    Interviewees described real-time editing with travel companions as one of the clearest benefits of using a planner.

    DESIGN RESPONSE

    We kept collaboration central to trip planning by supporting shared trips and real-time editing with travel companions.

03 / PUBLISH

Turning one trip into a starting point for another.

We designed a reuse flow where one traveler could publish a completed itinerary, another could discover and copy it, then adapt that copy without changing the original.

TRIP REUSE FLOW

Traveler A Plan → Travel → Publish ↓ Traveler B Discover → Copy → Modify → Travel

PRIVACY DECISION

When a trip is published, only selected trip content becomes visible to others. Personal and sensitive details stay private.

Visible to others

  • Itinerary
  • Tags
  • Highlights
  • Public notes

Stays private

  • Expenses
  • Private notes
  • Hotel / flight details
  • Personal travel details

CURRENT CONSTRAINT

The value of this flow depends on having enough useful published trips, which remains an early-stage challenge.

Bluprint Publish screen

04 / AI PLANNING

Adding AI without letting AI become the product.

AI wasn’t part of the original MVP. Once we confirmed it was feasible, we explored whether it could make Bluprint useful not only for travelers who enjoy planning, but also for people who find planning overwhelming.

DECISION

A guided flow, not an open-ended chatbot.

A structured flow gave users more control over what AI generated and made the output easier to review before adding it to their trip.

AI FLOW

Preferences → Generate → Review → Add to trip

Generated suggestions stayed separate until users reviewed and chose what to add to their plan.

PRODUCT CONSTRAINT

Model/API cost also pushed us toward a scoped, structured experience rather than using AI across every part of the product.

AI PLANNING / WALKTHROUGH

05 / SHIPPING

Designing Bluprint was only part of shipping it.

Building with a developer meant working through authentication, subscriptions, store requirements, and production edge cases that didn’t exist in our prototypes.

App Store · Google Play · Sign in with Apple · In-App Purchases · Production QA

REAL-WORLD PROBLEM SOLVING

Sign in with Apple

PROBLEM

During App Store review, we identified that returning Apple users might not receive a name after their first authorization. Because Bluprint required a Display Name, this could prevent users from completing onboarding.

DECISION

We made Display Name optional, saved Apple’s name when available, and used the Bluprint username as a fallback.

Shipping changed my definition of done from a polished screen to a product that could actually be released.

06 / REFLECTION

What I’d do differently today.

QUESTION THE FEATURE BEFORE OPTIMIZING IT

AI became one of Bluprint’s most developed features, but we invested in refining recommendations before we had enough evidence that AI planning was creating meaningful repeat value. Looking back, I would validate the core value of AI earlier before adding more complexity and model cost.

MEASURE BEFORE EXPANDING

We shipped with too little behavioral data. We could build and refine the product, but we had limited visibility into where users dropped off, what they returned to, or whether features like Publish, Copy, and AI were creating repeat value. If I did it again, I would define key events and success signals earlier, then use that evidence to decide what to refine, expand, or remove.

If I had another month with Bluprint, I wouldn’t add another feature. I’d make the product easier to enter, easier to use, and easier to measure.

MORE WORK

Explore other projects.

← Back to Home