BookMyShow

This redesign focuses on the four moments a BookMyShow booking stops being straightforward — a high-demand sale, a cancellation, a refund, and an uncertain final price — and asks the same question of each one: what's the earliest honest thing this screen could say?

UX Redesign

Ticketing

Overview


What's the earliest honest thing this screen could say?


A focused redesign of four moments where a BookMyShow booking becomes uncertain — during a high-demand sale, a cancellation, a refund, or an unclear final price.

Overview


What's the earliest honest thing this screen could say?


A focused redesign of four moments where a BookMyShow booking becomes uncertain — during a high-demand sale, a cancellation, a refund, or an unclear final price.

The evidence


Three real, public incidents, and a lot of overlapping user complaints, pointed at the same pattern: something goes uncertain, and the platform's response is reactive, not anticipatory.


  • September 2024 — the Coldplay Mumbai ticket sale crashed within minutes of going live; the concerts themselves were in January 2025.

  • January 2026 — the India–Pakistan T20 World Cup ticket sale crashed the same way, over a year later.

  • June 2026 — a Hyderabad consumer court ordered BookMyShow to pay ₹12,000 (₹10,000 compensation, ₹2,000 costs) for not notifying a customer a screening was cancelled before he arrived at the theatre. BookMyShow had refunded the ₹207 ticket price the next day — the ruling was specifically about the missing notice, not the refund.

The evidence


Three real, public incidents, and a lot of overlapping user complaints, pointed at the same pattern: something goes uncertain, and the platform's response is reactive, not anticipatory.


  • September 2024 — the Coldplay Mumbai ticket sale crashed within minutes of going live; the concerts themselves were in January 2025.

  • January 2026 — the India–Pakistan T20 World Cup ticket sale crashed the same way, over a year later.

  • June 2026 — a Hyderabad consumer court ordered BookMyShow to pay ₹12,000 (₹10,000 compensation, ₹2,000 costs) for not notifying a customer a screening was cancelled before he arrived at the theatre. BookMyShow had refunded the ₹207 ticket price the next day — the ruling was specifically about the missing notice, not the refund.

Proposed Changes


Price clarity


Fees and taxes often surface only at the final payment screen, after seats are already picked — a common pattern across ticketing platforms generally, and one I designed against as a hypothesis, not a confirmed finding specific to BookMyShow.


I moved the estimated all-in total to the seat-selection screen — not a promise of the exact final number, since fees can vary by tier, but an honest early estimate instead of silence until the last step.

Proposed Changes


Price clarity


Fees and taxes often surface only at the final payment screen, after seats are already picked — a common pattern across ticketing platforms generally, and one I designed against as a hypothesis, not a confirmed finding specific to BookMyShow.


I moved the estimated all-in total to the seat-selection screen — not a promise of the exact final number, since fees can vary by tier, but an honest early estimate instead of silence until the last step.


Demand-state communication


Both crashes above shared the same shape: no visible explanation, just a failure. People refreshing blindly, not knowing if they were still in line or already locked out.


I designed a real queue-status state instead — position, an estimated wait, explicit permission not to refresh. This doesn't fix the underlying infrastructure problem; it changes what the wait feels like while it's happening.


Demand-state communication


Both crashes above shared the same shape: no visible explanation, just a failure. People refreshing blindly, not knowing if they were still in line or already locked out.


I designed a real queue-status state instead — position, an estimated wait, explicit permission not to refresh. This doesn't fix the underlying infrastructure problem; it changes what the wait feels like while it's happening.


Cancellation handling


A Hyderabad court ruled against BookMyShow specifically because a customer wasn't told a screening was cancelled before he traveled to the theatre — the refund itself wasn't the issue; the silence beforehand was.


I designed a cancellation flow that notifies someone immediately, before they've left home, with one-tap rebooking or refund built into the notification itself.


Cancellation handling


A Hyderabad court ruled against BookMyShow specifically because a customer wasn't told a screening was cancelled before he traveled to the theatre — the refund itself wasn't the issue; the silence beforehand was.


I designed a cancellation flow that notifies someone immediately, before they've left home, with one-tap rebooking or refund built into the notification itself.


Refund clarity


BookMyShow's cancellation flow offers a real choice between refunding to your original payment method or BMS Cash wallet credit. Reviews describe people picking the wrong option by mistake and struggling to reverse it — a clarity problem in how the choice is presented, not a confirmed default.


I designed the choice to be visually unambiguous, with original payment as the clearer, more prominent option, and a concrete timeline shown up front: 5-7 working days to source, versus a few hours to wallet.


Refund clarity


BookMyShow's cancellation flow offers a real choice between refunding to your original payment method or BMS Cash wallet credit. Reviews describe people picking the wrong option by mistake and struggling to reverse it — a clarity problem in how the choice is presented, not a confirmed default.


I designed the choice to be visually unambiguous, with original payment as the clearer, more prominent option, and a concrete timeline shown up front: 5-7 working days to source, versus a few hours to wallet.


Beyond uncertainty, I looked at friction.


Not every friction point was about uncertainty.

I also explored the booking flow itself — particularly the moment food add-ons interrupt someone who is trying to complete a purchase. I tested a faster path that keeps add-ons available without making them a required stop on the way to payment.


Beyond uncertainty, I looked at friction.


Not every friction point was about uncertainty.

I also explored the booking flow itself — particularly the moment food add-ons interrupt someone who is trying to complete a purchase. I tested a faster path that keeps add-ons available without making them a required stop on the way to payment.

What I'd test


  • Does an early price estimate change checkout completion, and does it change what people add on, in either direction?

  • Does moving food add-ons post-booking drop attach rate enough to matter?

  • Does visible queue status reduce complaints even when the crash itself isn't prevented?

  • Does earlier cancellation notice reduce the specific complaint the Hyderabad case was about — not cancellations generally, just the lack of warning?

  • Does an original-payment default meaningfully hurt the repeat-usage BookMyShow may currently get from wallet credit?

What I'd test


  • Does an early price estimate change checkout completion, and does it change what people add on, in either direction?

  • Does moving food add-ons post-booking drop attach rate enough to matter?

  • Does visible queue status reduce complaints even when the crash itself isn't prevented?

  • Does earlier cancellation notice reduce the specific complaint the Hyderabad case was about — not cancellations generally, just the lack of warning?

  • Does an original-payment default meaningfully hurt the repeat-usage BookMyShow may currently get from wallet credit?

What redesigning someone else's product taught me


Designing something new (Atelier, ToneMatch) means inventing the constraints. Redesigning an existing, live product means most of the interesting constraints are ones you can't see from outside — I don't know if BookMyShow's checkout is structured this way by deliberate business tradeoff, technical limitation, or just unprioritized. What I could do honestly, without inside access, was read the real complaints carefully, find one consistent pattern across three independent public incidents, and design toward that pattern specifically — not toward a generic "ticketing apps have friction" assumption.

What redesigning someone else's product taught me


Designing something new (Atelier, ToneMatch) means inventing the constraints. Redesigning an existing, live product means most of the interesting constraints are ones you can't see from outside — I don't know if BookMyShow's checkout is structured this way by deliberate business tradeoff, technical limitation, or just unprioritized. What I could do honestly, without inside access, was read the real complaints carefully, find one consistent pattern across three independent public incidents, and design toward that pattern specifically — not toward a generic "ticketing apps have friction" assumption.