What I'd have measured
The metric we agreed on
In-app activity bookings vs. bookings that used to need a phone call.
No made-up conversion number. I don't have it. Engagement ended before development.
Took Booking Off the Phone, Made Discovery Personal
A booking flow that had to leave the phone behind
Travel & HospitalityiOS & Android
A tourism app so visitors could book in-app instead of calling the front desk. The home feed matches the trip they came for.
Context
Product Designer (Solo)Discovery-to-HandoffiOS & Android
If reception didn't pick up, the booking was gone.
What we found
People found stays and activities online, then called to book. Reception missed a lot of those calls.
What this page covers
The client left after handoff, before development. No live data. Just the reasoning, and what I would've measured.
Two problems
Booking lived on a phone call
Explore happened on the web. Book happened only if someone answered. Missed call, lost booking.
Same home for every trip
A golf trip and a family weekend need different homes. One feed meant most of what people saw wasn't for them.
Flow before screens
I mapped signup, how many questions, where skip lives, and what home does with those answers.
- Guest mode sits next to social and email signup. An account shouldn't block a look around.
- The quiz is chips, not a form. Golf and food can both be true.
- Skip exists. It's just not the default.
I went straight to high-fidelity. A wireframe pass first would've been cheaper.
Five questions
Purpose, destinations, activities, stay, interests. Each step is chips with a min and a max. Enough to personalize, not so many that the answers blur.
- Travel purpose
- Destinations
- Activities
- Preferred stay
- Special interests
After onboarding
Home follows the answers
Hero, bookings, stories, dining, activities, Plan Your Stay. They all shift off onboarding. If home didn't change, the quiz was just friction.
- Stories
- Explore
- Deals
- Dining
- Event page
.png&w=3840&q=75)
-1.png&w=3840&q=75)
-2.png&w=3840&q=75)
-3.png&w=3840&q=75)
-4.png&w=3840&q=75)
Design Solution
Signup through onboarding, then Explore, Deals, Dining.
Login
My role
Solo product designer. Engagement ended at handoff.
DiscoveryOnboardingHomeExploreDealsDiningHandoff
What I'd do differently
- I'd do a low-fi pass first. Some chip details got over-designed because the structure wasn't locked.
- Log drop-off early, so if a client leaves mid-project there's still a number to talk about.
Discovery project. Client requirements, my design work. Ended after high-fidelity handoff, before development.
Check out more work
SaaS · AI · Web App · Creative Testing
Designing an AI Platform to Validate Ad Creatives Before Media Spend
BrandPulse helps advertisers validate images, videos, text, and HTML5 banners with real audiences before launching campaigns — so marketers get data-backed insights instead of spending on assumptions.
View case study
NGO · Web Based Dashboard
Reduced Administrative Workload by 40%
A comprehensive healthcare management platform that streamlines program administration, case management, service tracking, and performance reporting through a centralized dashboard.
Coming soon