Discovery needs enough context to invite exploration
The Explore state uses destination imagery, categories, and concise location cues to help a traveler decide what to inspect next.
Back to Work
Travel discovery concept
Tripling: From Destination Discovery to Hotel Evaluation
A mobile travel concept that helps people discover destinations, inspect a hotel in context, and create an account when they are ready to continue.
AudienceB2C
DomainConsumer mobile · Travel
RoleProduct designer
PlatformMobile
Year2022
ScopeCase study and prototype
Reading time4 min
Product evidence
The screens below cover Explore, hotel details and account creation. There is no public interactive prototype.
30 Second Summary
DESIGN MOVE
Delay account creation until after destination discovery and hotel evaluation so visible value precedes commitment.
EVIDENCE
Three product screens show Explore, hotel evaluation, and account creation states.
LIMITATION
The documented scope ends at account creation and does not cover the later travel experience.
Overview
A focused mobile travel discovery concept.
Tripling helps people explore destinations, evaluate a hotel, and create an account when they are ready to continue. I designed the available discovery progression and the supporting mobile interface.
Problem
Travelers needed useful context before creating an account.
People should be able to explore a destination and inspect a hotel before being asked to create an account. The concept stops at sign up; itinerary editing and booking are outside its scope.
Problem and context
The documented journey moves from destination discovery to hotel evaluation, then account creation.
The documented scope covers three moments: destination discovery, hotel evaluation, and account creation.
Evaluation needs a clear shift from inspiration to detail
The hotel state brings the selected property, imagery, and descriptive context into a more deliberate comparison moment.
Account creation should follow visible value
The sign up state appears after the product has established a destination and hotel context, not as the first demand in the journey.
Product sequence
Discover a destination, evaluate a hotel, then create an account.
Three product screens define the documented scope without implying itinerary editing, day planning, maps, navigation, or booking.
01
Browse destinations and travel themes.
The Explore state creates an inspiration layer with destination imagery and recognizable categories.
02
Inspect a hotel before committing further.
The hotel detail state shifts the user from broad inspiration to one concrete property and its supporting context.
03
Create an account when the journey has earned it.
The sign up state provides a continuation point after the user has already seen the product’s discovery and evaluation value.
Key discovery decision
When should the experience ask a traveler to create an account?
The account request is more credible after the product has established a clear destination and hotel context.
Question
How can the concept preserve momentum before asking for commitment?
Signal
An early sign up gate would interrupt inspiration before the traveler understands what the product offers.
My decision
Let people explore destinations and inspect a hotel before presenting account creation as the next continuation step.
Why
The request feels earned when the product has already helped the traveler move from broad interest to a specific option.
Product consequence
Discovery and hotel evaluation remain visible proof of value before the account state appears.
Boundary
This scope does not cover itinerary editing, day planning, booking, maps, or navigation handoff.
Reflection
Make the account request worth continuing
Destination discovery and hotel details give people a reason to continue before the product asks them to create an account.
Next project
Support Portal
Support Portal helps agents identify a customer concern and interpret the context needed for the next action.
