Treddar

Designing confidence into every journey — making intercity travel predictable and trustworthy from search to arrival.
travelbookingseat selection
Role
UI/UX
Focus
Transactional confidence
Impact
increased confidence in travel decisions
Treddar
TREDDAR

DESIGNING A SIMPLER WAY TO DISCOVER, COMPARE AND BOOK INTERCITY TRAVEL.

Turning a traditionally fragmented travel-planning experience into a clearer mobile journey.

ROLE
UI/UX Designer
PRODUCT
Treddar
PLATFORM
Mobile Application
FOCUS
UX Strategy · Mobile UX · Booking Experience
TREDDAR
BUS A08:00
PRICE₦ 4,500
BUS B10:30
PRICE₦ 5,200
BUS C14:00
PRICE₦ 4,900
DECISION
ONE CLEAR CHOICE.
THE JOURNEY STARTS BEFORE THE BUS MOVES.

Planning an intercity trip can involve more uncertainty than the journey itself.

A traveller needs to know which routes are available, which agencies operate them, when they leave, how much they cost, whether seats are available, and how to secure a booking. The problem isn’t necessarily a lack of options. It’s the effort required to turn those options into a confident decision.

BUS A
08:00
PRICE
₦ 4,500
BUS B
10:30
PRICE
₦ 5,200
BUS C
14:00
PRICE
₦ 4,900
FROM SCATTERED OPTIONS → TO ONE CLEAR DECISION
WHY TREDDAR?

Treddar brings the travel-booking journey into a digital experience where travellers can search for available trips, compare options, select a journey, complete a booking and receive a digital ticket.

The product capability is straightforward but valuable: it helps travellers find available seats, compare agencies, compare prices and departure times, book trips, receive digital tickets, and use mobile payment with English/French support. The design challenge was to make that process feel orderly rather than fragmented.

WHAT TREDDAR BRINGS TOGETHER
DISCOVER
→
COMPARE
→
BOOK
→
PAY
→
TRAVEL
THE DESIGN QUESTION
HOW MIGHT WE MAKE
INTERCITY TRAVEL BOOKING
FEEL SIMPLE AND CERTAIN?

I wanted the experience to reduce the amount of mental work required before a traveller could commit to a trip. Instead of making people repeatedly search, compare and reconstruct information, the interface should progressively give them what they need to make the next decision.

WHERE?
→
WHEN?
→
WHICH OPTION?
→
WHO?
→
HOW TO PAY?
→
CONFIRMED?
I STARTED WITH THE JOURNEY, NOT THE SCREENS.

Before thinking about individual screens, I broke the experience into the decisions a traveller actually needs to make. That gave me a much clearer way to think about the interface.

01
DISCOVER
Where can I go?
02
COMPARE
Which option is right?
03
DECIDE
Which journey do I trust?
04
BOOK
What am I actually paying for?
05
CONFIRM
Where is my ticket?
WHO IS THE EXPERIENCE FOR?

I designed around travel intent rather than demographics.

THE PLANNER
THE PLANNER
“I know when I want to travel. I just need to find the right option.”

GOAL Plan ahead with confidence.

NEED CERTAINTY

PAIN POINT Unclear availability and scattered travel information make planning harder.

DESIGN RESPONSE
Show the important trip information early and make the booking path predictable.
THE FLEXIBLE TRAVELLER
THE FLEXIBLE TRAVELLER
“I care about price and departure time. Show me my options.”

GOAL Find the best option for their priorities.

NEED COMPARISON

PAIN POINT Different agencies, prices and schedules can be difficult to evaluate together.

DESIGN RESPONSE
Make trip cards highly scannable and comparison-friendly.
THE LAST-MINUTE TRAVELLER
THE LAST-MINUTE TRAVELLER
“I need to know what is available right now.”

GOAL Find and secure a trip quickly.

NEED SPEED

PAIN POINT Last-minute travel creates greater uncertainty.

DESIGN RESPONSE
Keep search, availability and booking steps focused.
THE RETURNING TRAVELLER
THE RETURNING TRAVELLER
“I don't want to repeat the whole process every time.”

GOAL Book with less friction.

NEED SIMPLICITY

PAIN POINT Repeating information makes returning journeys feel unnecessarily long.

DESIGN RESPONSE
Keep the experience familiar and reduce unnecessary decision-making.
THE JOURNEY I WAS DESIGNING FOR.
01
DISCOVER
Question
What can I take?
Emotion
Uncertainty
Opportunity
Clear route and date selection.
02
COMPARE
Question
Which one works for me?
Emotion
Evaluation
Opportunity
Scannable trip information.
03
SELECT
Question
Is this the right journey?
Emotion
Decision
Opportunity
Strong route and agency clarity.
04
BOOK
Question
Am I booking the right thing?
Emotion
Caution
Opportunity
Strong booking summary.
05
PAY
Question
Did my payment work?
Emotion
Concern
Opportunity
Clear confirmation.
06
CONFIRM
Question
Where is my ticket?
Emotion
Relief
Opportunity
Immediate digital ticket.
WHAT THE EXPERIENCE NEEDED TO DO WELL.
MAKE AVAILABILITY VISIBLE.

Travellers need to know what is actually possible before they can make a decision.

MAKE COMPARISON EASY.

Showing options isn’t enough. The differences between them need to be immediately understandable.

CARRY CONTEXT FORWARD.

Once a traveller has selected a route, the interface shouldn’t make them reconstruct that decision at every step.

END WITH CERTAINTY.

After payment, the user needs an immediate and unmistakable confirmation.

THE OPPORTUNITY WASN’T JUST BOOKING.

The larger opportunity was bringing several moments of the travel decision into one coherent experience.

DISCOVERY
COMPARISON
BOOKING
PAYMENT
CONFIRMATION
THE RULES I DESIGNED BY.
01
SHOW THE DECISION
02
KEEP THE JOURNEY MOVING
03
REDUCE UNCERTAINTY
04
MAKE IMPORTANT INFORMATION SCANNABLE
05
CONFIRM EVERYTHING IMPORTANT
I DESIGNED THE FLOW AROUND DECISIONS.
HOME / SEARCH↓TRIP RESULTS↓TRIP DETAILS↓PASSENGER DETAILS↓PAYMENT↓DIGITAL TICKET
BEFORE THE POLISH, I NEEDED THE FLOW TO WORK.

I intentionally kept the structure simple. The important question was not whether the screen looked finished; it was whether the user could understand the next decision with minimum effort.

SCREEN 01
SEARCH
Keep the first decision simple.
SCREEN 02
TRIP RESULTS
Make comparison scannable.
SCREEN 03
BOOKING
Carry route context forward.
THE DESIGN DECISIONS THAT MATTERED.
01, SEARCH

The search experience needed to get out of the user’s way. The first question is simple: where are you going? So the interface gives route, date and passenger selection a clear priority.

TREDDAR
SEARCH
FROM
Buea
TO
Douala
DATE
Select date
PASSENGERS
1
02, TRIP RESULTS

The results screen is where the traveller moves from searching to deciding. That meant the information hierarchy mattered: agency, departure, arrival, price and availability. The card needed to make these differences scannable.

AFC Express7 seats left
Departure08:00
Price₦ 5,500
A2M Travel11 seats left
Departure10:30
Price₦ 4,900
Nego Travel6 seats left
Departure14:00
Price₦ 5,200
03, TRIP DETAILS

Before payment, users should have a final opportunity to verify what they’re booking. The interface needs to answer the last questions before commitment.

BUEA → DOUALA
CONFIRMED
AgencyAFC Express
Departure08:00
Arrival11:00
Price₦ 5,500
SeatA12
04, PAYMENT

Once the traveller has made the decision, the interface should not introduce unnecessary complexity. Payment needed to feel like the last step, not another layer of uncertainty.

BOOKING SUMMARY
Amount₦ 5,500
Payment methodMobile Money
CONFIRM PAYMENT
05, DIGITAL TICKET

The booking ends with reassurance. The user needs to know the trip is confirmed and their details are ready to travel with.

TREDDAR
BOOKING CONFIRMED
ROUTEBUEA → DOUALA
AGENCYAFC Express
DATE12 Jul
TIME08:00
PASSENGER1 Traveler
BOOKING CODETRD-XXXX
READY TO TRAVEL
THE FINAL INTERFACE.

The final experience is built around one continuous booking flow: search, results, details, payment and ticket confirmation. Mobile remains the hero because the product lives in real travel moments.

TREDDAR
SEARCH
FROM
Buea
TO
Douala
DATE
Select date
PASSENGERS
1
HOME
Search first
SEARCH
Route & date
RESULTS
Trip comparison
DETAILS
Passenger + route
PAYMENT
Secure checkout
TICKET
Booking confirmation
DESIGNING A LANGUAGE THAT FEELS LIKE MOVEMENT.

The visual identity needed to communicate travel, movement, confidence, energy and clarity. The design uses vibrant gradients, bold typography, route lines and ticket-inspired shapes to give the app a sense of forward motion without looking generic or over-engineered.

THE STORY HAD TO WORK ON EVERY SCREEN.
PHONE
TABLET
DESKTOP PRESENTATION
FROM SCREEN TO JOURNEY.
BOOKING FLOW
SEARCH→
RESULTS→
SELECT→
BOOK→
PAY→
TICKET
TREDDAR
SEARCH
FROM
Buea
TO
Douala
DATE
Select date
PASSENGERS
1
VIEW TREDDAR ON GOOGLE PLAY →
WHAT THE DESIGN CHANGED.
CLEARER DISCOVERY

The user can begin with a route instead of navigating through complexity.

BETTER COMPARISON

Trip information is structured around the decision.

SIMPLER BOOKING

The flow progressively carries context forward.

STRONGER CONFIRMATION

The digital ticket provides a clear endpoint.

WHAT I TOOK AWAY FROM TREDDAR.
COMPARISON IS A DESIGN PROBLEM.

Showing more options doesn’t automatically make a decision easier. The interface has to help users understand the differences between those options.

GOOD BOOKING FLOWS REDUCE MENTAL WORK.

Every time the user has to stop and reconstruct information, the experience becomes heavier. Carrying context forward became one of the most important principles in my approach.

CONFIRMATION IS PART OF THE EXPERIENCE.

The moment after payment matters just as much as the moment before it. A user shouldn’t have to wonder whether the transaction worked.

MOBILE UX IS ABOUT THE MOMENT.

Travel happens in real situations, while planning, waiting, moving or preparing to leave. That made clarity and speed particularly important.

THE BEST BOOKING EXPERIENCE
IS THE ONE THAT LETS YOU
STOP THINKING ABOUT BOOKING.
And start thinking about the journey.

Next project

DYNAMIS
View next →