NAVIGATION / 2026 05 DESTINATIONS

PRODUCT DESIGN · UI/UX · DEVELOPMENT

MyBus Finder.

A responsive bus information experience designed to help people in Singapore quickly find nearby bus stops, check live arrival timings and access the bus information they need while travelling.

ROLE UI/UX Designer & Developer
PRODUCT Public Transport Web App
PLATFORM Desktop & Mobile
DATA LTA DataMall

01 / CHALLENGE

Bus information matters most when you need it now.

MyBusFinder was designed to reduce the steps between opening the product and knowing what to do next — whether that means finding a nearby stop, checking a bus arrival or looking up a known service.

01 Nearby first

Surface useful stops from the user's location.

02 Timing first

Make live arrivals easy to scan and compare.

03 Multiple paths

Support location, stop, service and repeat journeys.

02 / PRODUCT THINKING

Different starting points. One clear route.

MY ROLE UI/UX Design Information Architecture Front-End Development API & Technical Problem Solving
01 IMMEDIATE CONTEXT

Nearby me

Location → nearby stops → live arrivals

02 KNOWN SERVICE

I know the bus

Bus number → service search → route & stops

03 KNOWN LOCATION

I know the stop

Stop or place → stop search → live arrivals

04 REPEATED JOURNEY

I use this often

Saved bus → favourites → live arrivals

DESIGN PRINCIPLE Match the interface to the user's starting point.

03 / THE EXPERIENCE

More context on desktop. More focus on mobile.

RESPONSIVE APPROACH

The mobile version is not a shrunken desktop layout. It keeps the same four core tasks while prioritising what matters when someone is travelling.

MyBusFinder nearby buses desktop screen
01 Nearby buses
MyBusFinder bus service search desktop screen
02 Bus service search
MyBusFinder bus stop search desktop screen
03 Bus stop search
MyBusFinder favourites desktop screen
04 Favourites
MyBusFinder nearby buses mobile screen
Nearby buses
MyBusFinder bus service search mobile screen
Bus service
MyBusFinder bus stop search mobile screen
Bus stop
MyBusFinder favourites mobile screen
Favourites

04 / KEY DECISIONS

Three decisions shaped the whole experience.

01

Start with location.

Nearby travel already has context. Using location removes an unnecessary first search.

02

Separate stop and service search.

Searching for bus 67 is a different intent from searching for a stop near Orchard, so each gets a clearer path.

03

Put live timing in the hierarchy.

Arrival information changes what the user does next, so it needs to be easy to identify and refresh.

05 / DESIGN → BUILD

The happy path was only the beginning.

Turning the interface into a working product meant designing around live data, browser permissions, map rendering and failure states — not just polished screens.

LTA DataMall Leaflet Google Apps Script AI-assisted debugging
LIVE DATA

Arrival timings change constantly.

Refresh behaviour and current timing needed to remain visible instead of making stale information feel permanent.

GEOLOCATION

Location can fail.

Clear status messaging and manual search paths keep the product useful when permission is denied or delayed.

MAPS

Maps support the journey.

Route information remains useful even when map rendering or coordinate data needs troubleshooting.

AI WORKFLOW

Shorten the feedback loop.

AI helped me isolate bugs, test implementation ideas and iterate faster while I made the final product decisions.

06

OUTCOME & REFLECTION

A clearer interface came from understanding the system behind it.

MyBusFinder pushed me beyond designing a polished happy path. Working with live services made loading, errors, refresh states and location feedback part of the user experience itself.

If I continued the product, I would focus next on refining map interactions, edge cases and the reliability of live-data feedback.

BACK TO WORK