An upcoming server update will arrive with the next Melboard beta releases for iPhone and Android. It’s been rebuilt using a combination of the PTV API and GTFS feeds.
The main aim was to reduce the work needed to process the GTFS feeds on their own, making the server simpler and more streamlined. The new approach also helps return departure information sooner, especially when you’re refreshing a saved card.
In a side-by-side test of seven saved departure cards, the new service’s median response time was about 17% lower on the first request and 88% lower when the same request was repeated straight away. These figures measure how quickly the service responded in that test.
What to do after updating
There’s nothing you need to do now. Because of the significant changes to the server, Melboard will unfortunately need to start with a fresh Departures board when you install the next update. You’ll need to save your departure cards again. This is expected to be a one-off.
- Add your saved stops and stations again. Choose the routes and directions you use, then save each card.
- If you use Departure Groups, set them up again.
- If you’ve pinned a widget to a specific card, open the widget’s settings and reselect that card once you’ve added it back.
Melboard is making steady progress, and the beta will continue while I refine the iPhone and Android apps and the service behind them.
I’m continuing to fix bugs, improve the experience and explore new features, including refinements to the Apple Watch companion.
The server now combines GTFS feeds with the official PTV Timetable API. I’m continuing to refine how Melboard uses that information and improve the reliability of departures across the network.
There’s still work I want to do before Melboard leaves beta, so I’m not setting a release date just yet. I’ll share updates as things progress.
Tom
Hi everyone, and welcome. Thanks to everyone who’s been testing Melboard, sharing feedback and giving it a go.
Both the iOS and Android apps are now in a good place. There’s still work to do, particularly around data reliability, but I wanted to introduce myself, explain where things stand and talk a little about what comes next.
I’ve lived in Melbourne for over 20 years and use public transport every day. Melboard grew out of wanting an app that made checking my next departure easier, with an interface that felt modern and at home on both iPhone and Android.
A little about the data
Melboard currently uses Victoria’s GTFS timetable and real-time feeds. I’ve spent months working on the backend that turns those feeds into the departures you see in the app. There’s a considerable amount of work involved in interpreting the data, matching services and handling gaps or inconsistencies.
In my own testing at train stations and tram stops, I often find Melboard’s departures comparable to those shown by PTV and tramTRACKER. Sometimes they’re more accurate; sometimes they’re less accurate. There are also occasions when the feeds fail or provide incomplete information, which is frustrating when you’re trying to get somewhere.
That doesn’t mean every discrepancy is a feed problem. There are things for me to improve too, and reports from people using the app help me investigate those.
I’m also waiting for access to the PTV Timetable API v3. Once I have access, the longer-term plan is to assess how it can work alongside the existing GTFS feeds. Having another source may help, but I’ll need to test it before making promises about what it improves.
The status page and changelog
If you’re seeing Scheduled instead of Live, or departures for your train service don’t seem to be working, the status page is the best first place to check. It updates automatically to show the latest monitored feed health and can help you see whether there’s a wider GTFS data issue. It won’t necessarily explain every individual missing or incorrect departure, so please report those through the app’s beta feedback options or on r/melboard.
The changelog is also kept up to date with app changes, fixes and improvements.
I’ll use this blog for development posts and updates about what’s happening with Melboard.
Where the project is heading
I’m hoping there won’t be too many more beta rounds before Melboard is ready for release on the App Store and Google Play. That will depend on how the remaining testing goes. Pricing is still being worked out, with the aim of keeping it very accessible.
This is an independent, self-funded project. I cover the ongoing costs of developing and running Melboard myself, including hosting and the services and tools behind it. I’ve put roughly 800 hours into it so far, and it’s effectively become a full-time job. The app is developed here in Melbourne, and its backend server is hosted here too.
I use AI coding assistance to help develop both apps. I also want to be open about the work behind them: the design, testing, data investigation, server setup, website, name and original hand-drawn logo have all been my responsibility. This has been months of hands-on development, and I’m continuing to work on it every day.
Join the discussion
You’re welcome to use r/melboard for questions, suggestions, bug reports and discussion about Melboard or public transport in Victoria. I’ll also share development updates there when there’s something worth sharing.
If a departure looks wrong, the stop, route, direction and approximate date and time are particularly useful details. They give me something concrete to investigate.
Thanks again for the support and for helping test Melboard.
Tom