Skip to content
Vishnu Deva J

Joy Vision is a concept travel app for India that plans the trip, books the stay and helps you talk to locals in their language. Booking is easy. Getting through the trip in a language you don’t speak isn’t.

My role
Solo product designer
When
V1 2024 · V2 2026
Platform
iOS · iPhone 17
Scope
V1 audit → V2 redesign

By Vishnu Deva J · Updated

Joy Vision V2 on three iPhones: “Travel India in your own language”, with explore, stay and booking screens
Joy Vision V1 cover, 2024: discover, compare, book and live a trip, on three iPhones with travel reels, verified packages and a built-in translator
V1 · 2024V2 · 2026

Drag to compare the 2024 version with the 2026 redesign. Read the V1 case study

The short version · 30 seconds

The problem

V1 looked like every travel app. Its one unique feature, Translate, hid behind a small icon, and nothing was designed for when things went wrong.

What I did

Audited all 65+ of my 2024 screens, went back to the interviews, then rebuilt the app around Translate and a shorter, UPI-first checkout.

What changed

Planning a trip went from 10 screens to 3. Checkout went from 8 to 4. Thirteen error states now exist where V1 had none.

Screens to plan a trip
10 → 3
Checkout screens
8 → 4
To Translate, from anywhere
1 tap

01 · The problem

A Bengaluru couple in Gokarna or a Delhi family in Madurai can book the trip in minutes. The hard part comes after: ordering from a menu with no English, agreeing an auto fare at 6 am, asking where the bus stops. Often on weak signal.

What I found

  • Booking apps stop helping the moment you arrive
  • Translation apps know nothing about your trip
  • Nobody connects the two, and that gap is where Joy Vision fits
Joy Vision research summary: V1 interviews and survey results, a heuristic audit and a teardown of Airbnb, MakeMyTrip, Google Translate and Zostel

Joy Vision research summary: V1 interviews and survey results, a heuristic audit and a teardown of Airbnb, MakeMyTrip, Google Translate and Zostel

Joy Vision research summary: V1 interviews and survey results, a heuristic audit and a teardown of Airbnb, MakeMyTrip, Google Translate and Zostel
What V1’s interviews, survey and app teardown showed.

02 · What broke in V1

I went back to all 65+ V1 screens and checked each one against Nielsen’s usability heuristics, as if someone else had designed them. Three things stood out.

What I found

  • Translate, the reason to install the app, hid behind a header icon
  • Planning a trip took ten screens
  • Not one error state was designed. A failed payment just stopped
Joy Vision V1 from 2024: onboarding and travel suggestion screens

Joy Vision V1 from 2024: onboarding and travel suggestion screens

Joy Vision V1 from 2024: onboarding and travel suggestion screens
V1 (2024): the original screens.

03 · Three decisions

  1. Translate gets its own button

    Problem: the best feature hid behind a small icon.

    Fix: a raised button next to the dock, one tap from any screen. It costs a slot for future features, and it’s worth it.

  2. UPI first, cards second

    Problem: a card form and an OTP on weak signal.

    Fix: UPI apps sit on top and cards one tap below. Checkout drops from 8 screens to 4, with the full price and GST shown first.

  3. One sheet for where, when and who

    Problem: ten screens just to plan a trip.

    Fix: one sheet asks one question at a time, and answers fold into a summary you can tap. “I’m flexible” handles open dates.

Joy Vision V2 screens, “From a weekend idea to a booked room”: explore, stay and booked

04 · Before and after

Joy Vision V2 screens from 2026
Joy Vision V1 screens from 2024
V1 · 2024V2 · 2026

Drag the handle to compare. Left is V1 · 2024, right is V2 · 2026.

Translate
V1 (2024): A small icon in the header
V2 (2026): Its own button, one tap from anywhere
Planning a trip
V1 (2024): Ten screens
V2 (2026): One sheet, one question at a time
Paying
V1 (2024): Card form first, then an OTP
V2 (2026): UPI first, full price with GST up front
Checkout screens
V1 (2024): 8
V2 (2026): 4
When it fails
V1 (2024): Nothing designed
V2 (2026): 13 designed error states

05 · Site map

V1’s tab bar held Explore, a play icon, an unlabelled “+”, Wishlist and Settings. V2 keeps the four places people actually go, and puts Translate on a raised button where the thumb already rests.

What I changed

  • The play icon and the unlabelled “+” are gone
  • Trips holds bookings, the day-by-day plan and spend together
  • Translate has talk, camera and offline phrase packs in one place
Joy Vision site map: V1 tab bar versus V2 dock with a raised Translate button, and the Explore, Trips, Translate, Saved and Profile sections

Joy Vision site map: V1 tab bar versus V2 dock with a raised Translate button, and the Explore, Trips, Translate, Saved and Profile sections

Joy Vision site map: V1 tab bar versus V2 dock with a raised Translate button, and the Explore, Trips, Translate, Saved and Profile sections
The site map: four tabs, plus a raised Translate button.

06 · Core user flow

Sign in, pick what you enjoy, explore, search, choose a stay, review and pay, and your day-by-day plan is ready. Each screen does one job, and the dock keeps Translate, Trips, Saved and Profile one tap away.

What I changed

  • Search lives in one sheet instead of ten screens
  • Review and pay shows the full price with GST before you tap
  • UPI times out? Nothing is booked, and the room is held for 15 more minutes
Joy Vision core path in nine screens, from sign in to the day-by-day itinerary, plus the four dock destinations

Joy Vision core path in nine screens, from sign in to the day-by-day itinerary, plus the four dock destinations

Joy Vision core path in nine screens, from sign in to the day-by-day itinerary, plus the four dock destinations
The core path, plus the four places the dock keeps one tap away.

07 · Onboarding flow

Sign in, choose the languages you speak, pick the kind of places you love, and Home opens with picks that match. Sharing a few favourite places is what lets the app personalise from the very first session.

Why it works

  • Language comes first, because it powers Translate from day one
  • Interests replace a blank home with places you’d actually go
  • Google, Facebook and Apple sign-in, so nobody has to make a new password
Joy Vision getting-started flow: splash, sign in, choose language, pick favourite places, Home

Joy Vision getting-started flow: splash, sign in, choose language, pick favourite places, Home

Joy Vision getting-started flow: splash, sign in, choose language, pick favourite places, Home
Getting started: splash, sign in, language, favourite places, Home.

08 · Designing for bad days

V1 had no designed error states. V2 has thirteen, and each one says what happened, whether you lost anything and what to do next.

What I changed

  • Payment failed: says whether money was taken, and what to do next
  • No signal: Translate keeps working with offline phrase packs
  • UPI timed out: nothing is booked, and the room stays held
Thirteen Joy Vision error states, including payment failed, no signal and UPI timed out

Thirteen Joy Vision error states, including payment failed, no signal and UPI timed out

Thirteen Joy Vision error states, including payment failed, no signal and UPI timed out
Thirteen designed error states.

09 · Testing

V1 was tested with two volunteers, and what they said changed the stay page. Round two is planned with five weekend travellers aged 22 to 38, thinking aloud on an iPhone prototype for 30 minutes each.

What I’ll test

  • Find a stay in Goa under ₹4,000 a night and pay with UPI
  • Ask an auto driver the fare to the bus stand, in Kannada
  • Your payment just failed. What happened to your money?
Joy Vision testing plan: round one with two V1 testers and round two tasks for five weekend travellers

Joy Vision testing plan: round one with two V1 testers and round two tasks for five weekend travellers

Joy Vision testing plan: round one with two V1 testers and round two tasks for five weekend travellers
Round one findings and the round two test plan.

10 · How I’ll know it works

These are the numbers I’d hold the product to once it’s live.

Translate adoption · target
40%+
Time to first value · target
< 3 min
Money tickets · target
−30%

11 · What I’d do differently

  1. Test with more people. V1 was tested with two volunteers. V2 gets five people per round, and two rounds.

  2. Design offline from day one. Offline states came late and touched almost every flow. Next time, “no signal” goes in the brief.

  3. Bring an engineer in early. The UPI waiting screen and refund tracker depend on backend states, and that conversation belongs in week one.