A field journal through Tripling — a travel platform that carries a trip from first idea to last itinerary stop. Twenty-seven screens, read in order, the way a traveler would meet them.
Planning a trip means a hotel search in one tab, a spreadsheet for the itinerary, a group chat for who’s actually coming, and a maps app for what’s nearby once you land. The tools all exist. None of them talk to each other.
Tripling was a bet that discovery, booking, day-by-day planning and the social side of travel belong in one connected flow. What follows is that flow, walked end to end.
This wasn’t only a personal annoyance. The travel industry’s own numbers describe the same problem at scale — and one of its biggest players already tried a version of the fix Tripling proposes, then walked it back.
The point solutions that exist mostly specialize rather than unify. TripIt stores itineraries after you’ve already booked elsewhere; Wanderlog pairs a map with a collaborative planner; Roadtrippers is built specifically for driving routes. Each is good at one slice of the trip. None of them is asked to be the whole thing.
The first thing the app asks of you is nothing at all. A wordmark, a lake fading into the gradient, and two ways in — the five seconds of calm before any form appears.
Sign-in was designed twice: once empty, once mid-entry. This is the second one — a checkmark has already confirmed the username before the password field is even reached.
Every field in the sign-up flow carries the same inline check, with the terms checkbox gating the button. Nothing surprises you after the tap.
“We sent you an email!” A closed loop with one clear next step — not a silent redirect that leaves you wondering whether anything happened.
Browsing opens on a question, not a wall of listings: pick a category for your next adventure. A Popular sort up top, a featured strip below, two cards showing.
The sort dropdown is the control most apps fake. This one works: switch to Recently added and Mt. Catlin Hotel jumps to the front of the strip, live, on screen.
Three separate states were designed to prove it — closed, open, and applied — because an interaction isn’t designed until its middle frame is.
The full list runs 214 spots deep. Deals wear strike-through pricing, and every card carries distance, weather, and a review count — enough to judge without opening it.
Dates, amenities, price range, distance, room count — one tall sheet instead of a chain of pages, so narrowing the list never loses your place in it.
And when you don’t know what you’re looking for, the app stops asking: Nature’s Light, Cultural, Modern Life, Sun & Sand — moods with spot counts, not another sorted list.
Mt. Catlin Hotel, $967, Chicago. A photo carousel eight frames deep, live weather, and a rating that arrives with faces attached — 8.4 from six thousand votes, three of whom you can see.
The votes break open into reviews you can actually read — praise, complaints, a three-star “Not worth the hype!” left in — because a trustworthy average is one you can argue with.
The same hotel, now on a map: pinned, routed from where you stand, the full address written out, and a phone call one tap away. Get directions closes the loop between deciding and going.
Everything bookmarked collects in one place — 72 experiences at last count — instead of dissolving into a browser history. This is where trips actually start.
Editorial, not just algorithmic: “an exquisite trip you’ll rave about to your friends” is copy with a point of view, written the way a friend recommends — not the way a database returns.
The screen a spreadsheet usually ends up being: breakfast at 9:00, camel riding after, each block with its own photo and note. An itinerary that was designed, not exported.
Picking dates happens in two steps — month first, then the day on a proper calendar grid. Coarse before fine, which is how people actually think about when to travel.
Hawaii to Sevilla, Sevilla to Monaco, Atlanta to Marrakech — flights, trains and ferries as one running itinerary rather than a stack of confirmation emails in four inboxes.
The social layer treats a traveler as someone worth following: twelve thousand followers, forty-eight trips, a bio, a place. Travel apps usually skip this part; here it’s a first-class surface.
“Hey, ready for the trip?” A real conversation — text, a shared photo from 2016, a NEW divider marking where you left off. Built like messaging, not like a support-ticket log.
Follows, review likes, and the reviews themselves thread into one timeline instead of four notification types. The feed reads as what happened, not as what the app wants tapped.
Messages split active threads from the archive; settings sit behind three tabs. The unglamorous screens got designed too — that’s most of what makes a concept feel shippable.

The interface runs on two registers: a warm gradient for the moments that are about you — splash, sign-in, your profile — and near-black for the moments that are about the world — browsing, booking, planning.
Everything below is read out of the working file rather than eyedropped from a screenshot, so the values are the authored ones and the counts are real.
One three-stop ramp does every warm surface in the app. On the splash it carries a second layer: a greyscale lake plate at 15% opacity — which is why that screen reads as weather rather than as a photograph. Same treatment as the cover of this page.
The softer pink is what you press; the hotter one is what is currently on — the selected tab, the filled bookmark, the live dot on the nav.
Pure neutral, deliberately. With a gradient this saturated carrying the brand, any warmth in the greys would have muddied the dark screens — so the ramp stays untinted and the colour does all the talking.
One family, three weights, and the hierarchy carried by size and case rather than by adding faces. Medium does the bulk of the work; Bold appears only where a label needs to read as a control.
Every card in the app is the same object with different content: image, title, price and distance, then a meta strip. Learn it on the featured list and you already know how Saved, Explore and Bookings work.
Every flow above — plus the states that don’t make it into a case study — lives in the Figma prototype, exactly as designed.