01 / A simple question
A map full of buses is not necessarily an answer.
When I started building Find My Bus, I wasn't setting out to create a transport information platform. I wanted to answer a question most people in Canberra have probably asked at some point: where is my bus, and how much longer do I have to wait?
On paper, it sounded straightforward. Transport data exists. Put the vehicles on a map, give people a few controls and there you go.
Except a map with lots of moving dots doesn't necessarily tell you whether the bus you need is coming towards your stop, going in the opposite direction or has already sailed past while you were deciding whether to get another coffee.
That was the interesting part of the exercise for me. Not just how to show the data, but how to make it useful to the person standing at a bus stop.
I've worked on enough digital products to know that having information and helping someone make a decision are two rather different things. Find My Bus gave me another chance to put that thinking into practice.
02 / Start with the stop
Start with where someone is, not everything the system knows.
A transport data feed knows about routes, trips, stops, vehicle positions and plenty of other useful things. But someone opening a bus app isn't necessarily interested in its internal vocabulary. They usually know where they are and where they want to go.
So I built the experience around choosing a starting bus stop. You can search for a stop or an address, or choose to use your location. When the app finds nearby stops, it offers three to choose from rather than silently deciding which platform is yours.
That last detail matters. Two stops can be physically close and still serve different directions. Picking the closest one automatically might look clever right up until it sends someone to the wrong side of the road.
From there, the app can show routes serving the chosen stop. There is also an optional destination, which narrows the choices to direct services that serve the stops in the right order. The destination is useful when you need it, but it doesn't have to be another question everyone answers before getting started.
It's a small example of something I keep coming back to in UX: ask for what you need now, and leave the rest until it becomes useful.
03 / Next means next
The next bus should actually be the next bus.
One of the things I spent time refining was the order of the bus cards.
Once you've selected a route, you don't want an arbitrary collection of vehicles. You want to see which one is approaching your stop first, followed by the next one, and then the next. The list should reflect the journey, not the order the data happened to arrive in.
We also made room for a detail I particularly liked: up to one recently passed bus can appear at the top, clearly marked and greyed out.
Why show a bus that's already gone? Because sometimes that answers a question too. If you've just reached the stop, it's useful to know that you probably missed one rather than wondering why the next service looks so far away. What isn't useful is a list full of buses that left ages ago, or a passed bus that still looks like something you can select.
And when the system can't support a trustworthy passing time, it simply says Already passed. No pretending we know the exact minute just because a clock would look nice.
These are tiny decisions in a fairly small application. But they change whether the interface feels like a tool made for a person or a technical demonstration of available data.
04 / The map has a job
The map is there to help, not to steal the show.
I love a good map. Find My Bus uses one to show reported vehicle positions and the route a bus is following. It is a genuinely useful part of the experience.
But I didn't want someone to have to study a map and mentally work out which coloured marker was relevant before they could decide what to do.
Instead, the bus list does the early filtering. Choose a bus and the map moves to it. A short time later, the view can show the bus in relation to the selected stop. If you want to keep watching its progress, you can choose to follow it.
That interaction went through a few refinements. People should still be able to move and zoom the map themselves. Following a bus is helpful until the software starts wrestling the map back out of your hands.
On mobile, the search controls live in a slide-out panel so the map has room to breathe. The controls haven't disappeared; they're just not occupying half the screen once you've made your selection.
This is what I mean by leaving things out. The information is still there. It simply doesn't all have to compete for attention at the same moment.
05 / Be honest about data
An estimate is an estimate. Let's not dress it up as a promise.
Live transport information is a good reminder that reality doesn't always behave as neatly as a prototype.
Vehicle positions are reported in snapshots. The app checks for fresh information at regular intervals, but that doesn't mean a bus has sent a new position every time the screen refreshes. A marker can look precise while the information behind it is already getting old.
The arrival time shown by Find My Bus is an approximation based on the reported position and remaining route distance. It is not an official arrival prediction from Transport Canberra. I think that's worth saying clearly.
Similarly, if the app cannot work out a reliable value, showing an honest unavailable state is better than inventing a reassuring number. There is a surprising amount of design work in deciding what to say when the system doesn't know something.
We also had to think about direction. A bus that is geographically close may still be travelling away from the stop. Straight-line distance alone can be misleading, so the route and the sequence of stops matter.
For me, transparency isn't about covering the screen with technical disclaimers. It's about giving people enough context to make a sensible decision without giving them false confidence.
06 / Test the real question
A good test is surprisingly ordinary.
As the app took shape, I kept coming back to simple questions. Can I find the stop I mean? Can I tell which direction a route serves? Can I see the next approaching bus? What does the app tell me if I've just missed it?
They're not glamorous test scenarios. Nobody is going to put the greyed-out passed bus card works on the front of a conference programme.
But they expose the difference between a technically functioning feature and a useful experience.
A polished interface can still make someone perform far too much mental work. And a clever use of live data can still leave the person waiting at the stop unsure what to do next.
I don't want to present this little project as a formal user-research study. It was a personal build, with plenty of iteration and real-world questions guiding the changes. That distinction is important. But the habit of testing an experience against the decisions people actually need to make is one I'd carry into a much larger service.
07 / What I took away
Making something simpler can take more thought than adding another feature.
Find My Bus is still a small experiment, and it's not an official Transport Canberra service. I built it because I was curious, because I enjoy making useful things and because a very ordinary problem gave me something interesting to work through.
What stayed with me wasn't the map, the live feed or even getting a bus marker to move along the right route. It was the number of decisions involved in making those things feel straightforward.
Which stop comes first? Which bus should be at the top? When is a missed service helpful information rather than clutter? What can we honestly say about an estimated arrival? When should the map follow along, and when should it leave the person alone?
None of those questions is especially complicated in isolation. Together, they shape whether someone can open the app, understand what's happening and get on with their day.
Useful design isn't about displaying less for the sake of minimalism. It's about showing the right thing at the right moment, and making it clear what someone can do next.
If you're curious, you can try Find My Bus or read the original story of how I built it. Just remember, the bus itself is under no obligation to cooperate with my design decisions.