Understanding the Challenge
Hailing a bus is straightforward if you can see it coming. If you can't, the same trip becomes a run of unknowns. Is this the right stop, is that my route, will the driver see me waiting.
The wider problem sits between systems rather than inside any one of them. Ticketing, apps, signage and announcements each cover part of a journey, and the gaps between them are where riders get stranded. Hailo set out to close one of those gaps, and it had to feel dependable while doing it.
KEY REQUIREMENTS
1
Onboarding that works under pressure
People often sign up at the stop, in a hurry. The flow had to be quick to complete, easy to hear as well as read, and clear about what it asks for and why.
2
A hail you can trust
Hailing is the most important action in the app. The button and its feedback had to leave no doubt that the request had gone through.
3
Accessibility built in, not added on
Contrast, type size, touch targets and reading order needed to be part of the base design rather than a later pass over finished screens.
5
A way for riders to be heard
Riders needed a simple way to give feedback and report problems, so a young product could keep learning from real use.
6
Settings that are easy to change
Account details and access requirements had to be editable in a couple of taps, including choosing more than one access need.
Summary
Hailo asked for more than usability. It asked for trust, in a situation where a missed signal has real consequences. The work ran from research synthesis through iterative wireframing to a hi-fi prototype and a design system built to scale.
Hailo is now live on the App Store, running on Melbourne's Ventura network.
More works












