Many transit agencies assume that having a "transit app" means building a custom smartphone application from scratch. For most small and mid-size agencies, this is an expensive, time-consuming approach that is usually not the best use of resources.
The reality is that most of your riders already have a transit app — it is called Google Maps, Apple Maps, or another specialised transit app. The most effective way to reach riders through apps is to get your routes listed in the apps they already use, rather than asking them to download a new one.
That said, there are legitimate reasons to want a more dedicated presence — branded departure board displays, online ticket purchasing, real-time vehicle tracking on your own website. This guide covers all your options so you can choose the right approach for your agency.
Publishing your GTFS feed to Google Maps, Apple Maps, and other trip planners gives riders immediate access to your schedules and routes through apps they already trust and use daily. This is the fastest, cheapest, and highest-reach option for most agencies.
Cost: Free to submit. You need a valid, hosted GTFS feed.
Time to go live: Days to weeks after submission.
Rider reach: Billions of monthly active users across platforms.
See our guide on how to get your routes listed on trip planners to get started.
A white-label transit app is a pre-built application that a provider customises with your agency's branding — your logo, colours, and name. The underlying functionality (route maps, departure times, real-time tracking) is built and maintained by the provider. You pay a subscription or licensing fee.
White-label apps work best for agencies that want a branded presence in app stores but cannot justify the cost of custom development. Look for providers that support GTFS as their data format — this ensures your schedules and routes flow in automatically from your existing GTFS feed.
A custom app is built to your exact specifications by a development team. You own the code, choose the features, and control every aspect of the experience.
Custom apps are appropriate for large transit authorities with significant budgets and internal technical capacity. For small and mid-size agencies, the cost is usually prohibitive relative to the benefit of reaching a small fraction of your riders through a branded app.
A well-designed, mobile-optimised website can serve many of the same purposes as an app — route maps, departure times, service alerts, contact information — without the cost of app development or the friction of asking riders to download something. Riders can save your website to their home screen on both iOS and Android, creating an app-like experience.
A mobile website works best as a complement to Google Maps and Apple Maps listings, not as a replacement. Use it for information that is specific to your agency — route maps, contact details, fare information, news about service changes — and rely on the major mapping apps for journey planning.
Regardless of which app approach you choose, a valid GTFS feed is the foundation. It is what gets you into Google Maps and Apple Maps (Option 1), what feeds your data into a white-label app (Option 2), and what provides the schedule data for a custom app (Option 3). Without a GTFS feed, none of these options work well.
AddTransit helps you build and maintain that GTFS feed, and provides the hosting and API infrastructure that app developers need. Many agencies start with AddTransit to get listed on Google Maps, then layer additional features — online ticketing, real-time tracking, and eventually a branded app — as their digital maturity grows.
