← All work
00
UX case study · 2021

Ticketwise

Booking a ticket, without the doubt.

5days, start to finish
28high-fidelity screens
3usability sessions

Ticketwise is an online ticketing platform for B2B and B2C: organizers publish events and sell tickets, and people book seats for events they love. In a self-initiated five-day sprint, I tested why three people struggled to book in one ticketing app, then redesigned the purchase flow.

Role
Sole designerSelf-initiated · research, testing, UI
Duration
5 daysSeptember 2021
Platform
Android app28 high-fidelity screens
Tools
FigmaPen and paper
Sign up
Sign up
Home
Home
Seat selection
Seats
Local payment methods
Payment
E-ticket
E-ticket
01Problem & plan

Booking online felt harder than it should.

Ticketwise is an existing ticket-booking app. I wanted to know whether the experience itself was the barrier, so I tested it with three people, then redesigned it with a clearer UI and UX.

Bad UXMissing featuresSecurity issuesAesthetics are not great
The Ticketwise app before the redesign
BeforeThe app as I found it
Plan & goals

Is usability the real barrier?

Card payments, low-tech users and few incentives to go digital are common barriers to booking online. I planned interviews and usability tests to see whether the app itself was one of them, and what would convince people to book online.

Research plan: user details, demographics, familiarity with online booking, and three interview branches

Features to test

Log in & sign upBrowse eventsOpen an eventEvents nearbyBuy tickets & seatsPayment options
02Process

Research first, then design.

I set the process before touching a screen, and looped between sketches and low-fi until the purchase flow held up.

Process to follow: user research with usability testing, analysis and personas, then ideation, sketches, low-fi and high-fi
Step 1

User research

Usability tests, interviews, analysis, personas.

Step 2

Ideation

Ideas from research, competitors and UX practice.

Step 3

Story map

The purchase journey, step by step.

Step 4

Sketches & lo-fi

Paper concepts, then eight wireframes.

Step 5

Hi-fi

28 screens and a design system in Figma.

03Testing & analysis

Three participants, real booking tasks.

I ran in-person, qualitative usability tests with three participants on 15 and 16 September 2021, 20 to 40 minutes each, measuring task success. Two had never used a ticket booking app before.

Sign upBrowse eventsBook ticket / seatsPayment method
QuestionP1P2P3
Were you able to complete the booking from start to end?YesYesNo
Is the information clear enough to book without doubts? (1–5)21n/a
How was your experience while booking a ticket?It was OKEasy to understandDidn’t make any booking
Would you like to suggest any improvements?Tags on seatsAttachedPayment by hand
What do you think of the layout of the overall app?OKNeeds UX/UI improvementsLayout needs to be better
Would you use Ticketwise to book a ticket again?I will thinkYesNo
Participant 1 handwritten session notes, personal details blurred
Participant 2 handwritten session notes, personal details blurred
Participant 3 handwritten session notes, personal details blurred
01

Sign-up took too long

“There are too many fields; it would be good if there were social sign-ups.”

02

Events felt unsorted

“It would be better if there was a home page where different categories of events were listed.”

03

Payment raised doubts

“How will I know my bank account is safe if I enter my card details?”

Field notes from each session; personal details are blurred. Participants anonymized as P1–P3. The test measured the existing app, before the redesign. Quotes are edited from the session notes.

Analysis

What the sessions revealed.

Three themes came up across the sessions.

01

Trust issues

Participants were uncomfortable entering personal information, such as account numbers, into an app they had never heard of.

02

Missing key features

Several features were missing from the booking flow, making the experience hard to use.

03

Payment methods

Popular local methods like JazzCash and Easypaisa were missing, which participants found highly inconvenient.

04Personas

Who are the users, and what do they need?

After synthesizing the research, I created personas to keep users’ needs and frustrations in front of every design decision.

K

Kinza Urooj, 30

Student · MS Arts and Design · Islamabad

“I love attending music concerts and watching movies in cinemas with friends and family.”

Kinza spends most of her time with friends and attending different concerts.

Core needs
  • An app where people can buy tickets for different concerts
  • A safe and secure payment method
  • The option to cancel booked tickets when necessary
Frustrations
  • Buying tickets manually is frustrating
  • Tickets get lost, and there’s no entry without one
  • Tired of waiting in line to buy a ticket
A

Adeel Ahmed, 27

Student · MBA · Islamabad

“I love to watch movies on the big screen in the theater with friends.”

Adeel spends most of his time with friends and loves to watch every new movie in cinemas.

Core needs
  • An app to see upcoming movies and events and buy tickets
  • A secure payment method
  • A simple refund process
Frustrations
  • Buying tickets manually is getting old
  • When events get canceled, refunds are slow
  • Dislikes watching movies from the end rows
05Ideation

Ideas from research, competitors and UX practice.

I generated as many improvements as I could, then kept the ones that answered a finding from the sessions.

Ideation sticky notes: social sign-up, a categorized home page, e-tickets, seat tags, local payment methods, OTP verification, an events calendar with reminders
06Story map & lo-fi

One activity, nine steps, every detail.

Before wireframing, I mapped the whole job of buying a ticket: the activity, the steps in order, and the details each step needs. Two steps can fail, so the failure cases were mapped too.

Story map activity: Buy ticket for event
Story map steps: social login, select event, check availability, book seat, select payment, enter account details, enter OTP, seat booked, view and download ticket; failure cases: seats already booked, OTP mismatched
Story map details: connect social account, view event details, choose seat category and type, choose payment gateway, enter number and email, OTP verification, e-ticket
01

Nine steps, one goal

From social login to downloading the e-ticket.

02

Failure designed in

“Seats are booked” and “OTP mismatched” got their own states.

03

Details became screens

Seat class and type, payment gateway, number and email, OTP.

Sketches & lo-fi

From paper to eight wireframes.

I sketched two login and sign-up approaches and the ticket purchase flow on paper, then turned the purchase flow into eight low-fidelity artboards.

Paper sketches of login, sign-up and the ticket purchase flow
PaperTwo login and sign-up approaches, and the purchase flow
Low-fi purchase flow: event, seat selection, payment method, account, details, OTP, greetings, e-tickets
Lo-fiPurchase flow: event → seats → payment method → account → details → OTP → greetings → e-ticket
07Iterations

A first pass, then a lighter final.

My first high-fidelity pass put a solid magenta header on every screen. In the final version, screens turned white and magenta was kept for actions and selected states, so event photos and seat states stand out.

First high-fidelity pass with solid magenta headers
First passSolid magenta headers on every screen
Final · Home
01Final · Home
Final · Seats
02Final · Seats
Final · Payment
03Final · Payment
Final · E-ticket
04Final · E-ticket
08Sign-up & discovery

In with one tap, events by category.

Sign-up was the first complaint in testing, so the redesign uses social sign-up only. Home opens on featured events and categories, with filters for location, time and interests.

Sign up with Facebook, Google or Instagram
Home: featured events and categories
Discover: featured and upcoming events
Filters: location, time, interests
01

Social sign-up

Facebook, Google or Instagram, no form to fill.

02

Categories first

Fashion, food, music and trade shows on the home screen.

03

Filter by what matters

Current location, this week or next, concerts or sports.

09Event & seats

Pick a class, see exactly where you’ll sit.

Each event page shows the organizer, time, place on a map and ticket prices. Seat selection uses tabs for VIP, Gold and Economy, with every seat marked available, reserved or selected.

Event details, full length
01Event details · scroll inside
Seat selection: VIP
02VIP
Seat selection: Gold
03Gold
Three seats selected, total updated
04Seats selected
Decision

Tags on every seat

A participant asked for “tags on seats”, and another worried about who would sit next to their family. Seats are tagged M or F, so people can book next to someone they are comfortable with, and the total updates as each seat is picked.

10Payment

Local wallets, and a check before money moves.

Two key findings were trust and missing payment methods. Checkout now offers JazzCash, Easypaisa and UBL Omni next to cards, and asks for an OTP before anything is charged.

Payment method
01Payment method
Choose a wallet
02Choose a wallet
Mobile number
03Mobile number
Email for the ticket
04Email for the ticket
Enter OTP
05Enter OTP
Verifying
06Verifying
Booking confirmed
07Booking confirmed
Decision

Verification as reassurance

Participants didn’t trust an unknown app with their account details. Familiar wallets plus a visible OTP step and a “verifying” state show that nothing happens without their confirmation.

11Tickets & account

An e-ticket you can’t lose.

Kinza’s frustration was a lost paper ticket. Every booking becomes an e-ticket with seat numbers, date and a barcode, ready to download, next to a wishlist and a simple profile.

E-tickets with barcode
01E-tickets with barcode
Empty: no tickets yet
02Empty: no tickets yet
Empty wishlist
03Empty wishlist
Profile
04Profile
Side menu
05Side menu
No search results
06No search results
12Research to design

Every finding has a screen.

How each finding from the sessions shows up in the final design.

Finding

Too many sign-up fields

Social sign-up only, in one tap

Finding

Events felt unsorted

Home with categories, filters and nearby events

Finding

Trust issues

Familiar wallets, OTP and a “verifying” state

Finding

Missing local payments

JazzCash, Easypaisa and UBL Omni

Finding

Lost paper tickets

Downloadable e-tickets with a barcode

Finding

“Tags on seats”

M and F tags with clear seat states

13Design system

Magenta for action, gray for everything else.

A ten-step pink scale and a gray scale, Roboto with the Material type scale, and components for seats, cards, payments and tickets.

#A5025B
Pink · 900Style
#B7357C
Pink · 700 · primaryStyle
#DB9ABD
Pink · 300 · selectedStyle
#F6E6EF
Pink · 50Style
#1A1A1A
Black · 800 · textStyle
Typography · Roboto
Aa

Roboto with the Material type scale, from a 96px headline down to a 10px overline.

  • H5 · Event nameRegular 24
  • H6 · Screen titleMedium 20
  • Body 1Regular 16
  • ButtonMedium 14
  • CaptionRegular 12
Components
Seat states · available, reserved, selectedClass tabs · VIP, Gold, EconomyEvent cardsPayment methods & fieldsOTP verificationE-ticketFooter total + BuyFilter chipsNavbarEmpty states
Ticketwise design system: headers, tabs, inputs, buttons, seat states, lists, footer tabs, cards, payment fields, ticket, empty states, navbar, icons
14Outcome

A booking flow built on what people said.

A five-day research and redesign sprint. The redesign was not usability-tested again within those five days, so the numbers below describe the research and the design, not results after launch.

3

usability sessions, 20 to 40 minutes each

15–16 Sep 2021
1 of 3

could not finish a booking in the old app

Usability test
9

steps in the user story map, plus 2 failure states

Design file
28

high-fidelity screens

Design file
Lesson

Trust is a UX problem

Security worries showed up as hesitation in the flow, so the fix had to be in the flow too.

Lesson

Local wallets won

Familiar wallets were the clearest ask in testing.

Next time

Test the redesign

Repeat the same four tasks with new participants and compare completion and time.

That’s a wrap

Thanks for reading.

See the original case study on Behance.

Screens show demo events. Participants are anonymized. A self-initiated case study. Research and design by Muhammad Maavia, September 2021.

Did you like it?

Leave a like

A quick human check keeps likes honest. One like per visitor.

0 views0 likes