Case studies · Rail booking

Booking a Shinkansen in 30 seconds

Two of the official Shinkansen booking apps rate below two and a half stars on the Japanese App Store. We rebuilt the booking flow as a working prototype. It opens on the next train, and two taps book it.

Japanese App Store, 22 November 2026.

What goes wrong today

We read the low-rated reviews of the booking apps and studied how SmartEX, えきねっと and e5489 work. The same problems kept coming up.

購入決定ボタンを押した後に混み合っているなどと表示されたら購入完了していないものと思うのではないだろうか。

“If it says the system is busy after you press Buy, wouldn’t anyone assume the purchase hadn’t gone through?”

One-star review of えきねっとチケットレスアプリ, December 2025. The reviewer bought again 20 minutes before departure, ended up with two tickets, and paid a fee to cancel one.

ワンタイムパスワードが発行されるまでにアプリがタイムアウトで強制ログアウト

“Before the one-time password arrives, the app times out and logs me out.”

One-star review of EXアプリ, October 2021, from a traveller trying to get a QR ticket for two people at the gate.
  • Registration walls. SmartEX and えきねっと each need their own account, and e5489 asks for an email and a passcode for every booking.
  • Payment that fails at the last step. Foreign cards fail at 3-D Secure with vague or Japanese-only errors.
  • Many steps before a result. Direct trains may not appear unless the right search option is chosen.
  • Failures you can’t read. Guides tell you to check your reservation list after an error so you don’t book twice.
  • Fare confusion. Base fare, limited-express ticket, reserved or non-reserved, the Nozomi supplement.
  • Ticket pickup. Where to collect it, with which card, and whether the email is enough.
  • Fragmented systems. One trip can span operators whose sites each have different rules, and English that differs per site.

What we changed

One requirement shaped every screen: from opening the app with no ticket to holding a booked ticket in 30 seconds or less.

  1. It opens on the answer

    There is no search button. The first screen already shows the next trains for your last route, with the first to arrive picked out.

  2. Two taps

    Tap the train, then “Pay ¥14,720 and book”. Review and payment are one screen, and the button says exactly what it will do.

  3. Seats picked for the party

    Up to six passengers sit together, by the window where possible, and you see the seats before you pay. The seat map is one tap away. Oversized-baggage seats are marked and never assigned automatically.

  4. One price

    Each train shows one total for the whole party. The review screen breaks it into base fare, express surcharge and any Green or Gran Class surcharge.

  5. A booking exists or the screen says why

    After booking, Back returns to the timetable, not to the pay screen, so a second tap can’t book twice. Errors say what happened and what to do next, in plain English.

  6. The ticket is in the app

    The confirmation is the ticket, with train, car, seats and reference, and the Tickets tab keeps it. Nothing to collect.

  7. No account

    No sign-in, no email, no passcode. Shinkansen tickets aren’t named, so no passenger names are asked for either.

  8. English first

    Every screen is in English, with the Japanese station and train names beside them.

What’s in the prototype

One timetable for ten Shinkansen lines: 118 stations, 18 named services and nine trainsets with their real car layouts. Reserved, Green, Gran Class and non-reserved seats, wherever the real train has them. It works at 320 px wide and at the largest text size, in light and dark.

What it would take to make it real

JR doesn’t offer a public booking API: seat inventory, payment and ticketing all live inside the operators’ own systems. So this front end can’t sell a real ticket on its own. Making it real takes an operator, or a partner the operators authorise.

That is the point of the prototype. It shows what booking could feel like, built against the real constraints of the timetable, the fares and the cars. If you run a booking product in Japan, this is the kind of front end we build.