AS
← Work

E-Bilet

A mobile UX/UI concept for Turkey's intercity rail ticketing experience, focused on route search, timetable comparison and trip management.

2024UX/UI DesignFigma, Miro
MobileUX ResearchInteraction Design

E-Bilet users need to plan and manage intercity rail journeys under time pressure. The original experience made this harder by spreading key actions across unclear navigation, making timetable updates difficult to surface and hiding important travel details such as platform information. The redesign focuses on a clearer route-first flow supported by searchable stations, recent trips, timetable cards and trip-management states.

Where the experience broke down

01
Route planning friction
Users needed a clearer way to start a journey search and narrow down stations. Route planning felt more effortful than it needed to be.
02
Weak update visibility
Schedule changes, delays and platform details were not easy enough to locate. Travel information becomes most valuable when timing matters.
03
Fragmented trip management
Planning, saved trips and tickets needed to feel more connected as one continuous travel experience.
70%
reported navigation as somewhat difficult
Based on early evaluative research
60%
reported issues with timely travel updates
Based on early evaluative research
#1
use case was checking train schedules
Consistent across all respondents

A route-first task model

Instead of treating every screen equally, the redesign focuses on the moments where clarity matters most: starting a route search, comparing available journeys and keeping trip information within reach after booking. The app is organised around a route-first journey: users begin with a travel need, narrow it through station search, compare available departures and keep the journey accessible after booking.

Step 01
Enter route
Start with origin and destination, not buried menus.
Step 02
Select station
Support search and recent routes to reduce repeat entry.
Step 03
Compare departures
Make time, duration and route information scannable.
Step 04
Manage journey
Keep tickets and saved journeys reachable after booking.

Key flow: planning a journey

Early research and evaluative testing pointed to three recurring issues: navigation friction, weak visibility of travel updates and difficulty accessing platform information. The following screens show how the redesign addresses each moment in the rail journey.

Low-fidelity wireflow showing the broader app structure around route search, departure selection, ticketing, saved trips and support states.
Low-fidelity wireflow showing the broader app structure around route search, departure selection, ticketing, saved trips and support states.
Annotated journey walkthrough showing the four key flow states with UX annotations.
Annotated journey walkthrough: route input → station search → timetable results → trip management.
Research Signal
Navigation felt unclear
Core actions were spread across too many entry points.
UX Decision
Prioritise route planning
Make journey planning the dominant starting point.
Product Response
A cleaner entry flow
Timetable and route search become the primary first action.
Research Signal
Updates were difficult to locate
Delay, schedule and platform information lacked visibility.
UX Decision
Surface travel-day information in context
Bring updates closer to live, ticket or active trip.
Product Response
Better status visibility
Platform and change information appear at relevant journey states.
Research Signal
Comparing routes required too much effort
Users struggled to compare departures and filter by time.
UX Decision
Reduce decision effort
Structure results for quick scanning and comparison.
Product Response
Scannable timetable cards
Date-grouped results show time, duration, direction and availability.
Research Signal
Repeated travel tasks felt heavy
Users needed easier access to saved or recurring journeys.
UX Decision
Support reuse and continuity
Treat trips and tickets as a continuation of planning, not a separate dead-end.
Product Response
Trip and ticket management
Saved trips, travelcards and post-booking access reduce repeated setup.
Focus
Route-first structure
Priority
Time-sensitive clarity
Outcome
Lower travel friction
UX decision map showing research signals, design decisions and interface responses for the E-Bilet redesign.
UX decision map connecting the main travel-planning pain points to the redesign response.
Fragmented / Existing Flow
  1. 1.Open app
  2. 2.Browse tabs
  3. 3.Find route
  4. 4.Search stations
  5. 5.Review results
  6. 6.Check updates elsewhere
↳Unclear starting point
↳Travel-day information felt hidden
↳Comparing and filtering required extra effort
Redesigned Flow
  1. 1.Search route
  2. 2.Choose station
  3. 3.Compare departures
  4. 4.Manage journey
↗Route planning becomes the primary entry point
↗Results support faster comparison
↗Tickets, trips and updates stay closer to the active journey
Simplification
Fewer steps to the core task
Clarity
A stronger route-first structure
Support
Better visibility during travel
Before and after flow comparison showing the simplified E-Bilet route planning journey.
Before and after flow: a fragmented planning path is reduced into a clearer route-first journey.

Supporting UX improvements

↗
Recent and saved journeys
Designed to reduce repeat effort for frequent routes. Recent trips appear in station search to support commuting patterns.
↗
Tickets and travelcards
Grouped into clearer states so users can distinguish valid, expired and manually entered travelcards at a glance.
↗
Map and destination views
Included as secondary discovery tools, not the main planning mechanism. Route search remains the primary entry point.

Reflection

This project began as a student redesign exercise, but the strongest part of it remains the service-flow question: how can a rail ticketing app make time-sensitive travel tasks easier to complete? If I developed it further today, I would validate the route-planning flow with real users, simplify the information architecture further and refine how delays, platform information and trip changes appear across the journey. The strongest lesson from this project was that transport UX does not need more screens. It needs clearer prioritisation of the right moments.