How MaaS Apps Quietly Changed the Commute (and Where They Failed)

Around 2016 a lot of smart people decided the future of urban travel was a single app where you'd buy a monthly mobility subscription — some transit, some bike share, a few taxi rides — and never think about a car again. Investors funded it. Cities wrote it into strategy documents. Consultancies produced diagrams with a phone in the middle and spokes going out to every mode.

Almost none of those apps exist now.

What did happen is stranger and much less brandable. Mobility-as-a-Service quietly won by dissolving into things you already had on your phone, and the version that stuck looks nothing like the pitch decks.

You're already using one

Open your maps app, ask for directions across town, and look at what comes back. Walk five minutes to a stop, ride a specific bus, transfer, walk three more. Underneath that: a bike-share option with the number of bikes currently docked at the nearest station. Next to it, a rideshare estimate. Maybe a scooter, with its actual battery range.

That's MaaS. It's aggregated multimodal trip planning with live availability and, increasingly, the ability to unlock or book without leaving the app. The fact that it arrived inside a general-purpose maps product rather than a mobility startup is the whole plot twist.

Transit agency apps are the other quiet winner. A well-built regional transit app now sells fares, shows vehicle positions, handles service alerts, and in a growing number of regions lists bike share and scooters alongside the bus. Agencies got there because they already controlled the two hardest pieces: the fare system and the trust.

The plumbing, briefly

The reason your maps app can tell you when the bus arrives is a set of unglamorous open data standards, and they explain almost everything about which features work well and which feel half-finished.

GTFS — the General Transit Feed Specification — is a published format for schedules, routes, and stops. It started as a side project between a transit agency and Google and became the de facto global standard. Its realtime sibling carries vehicle positions, arrival predictions, and alerts. If a transit system publishes both, any app can consume them.

GBFS, the General Bikeshare Feed Specification, does the same job for docked and dockless fleets: where the vehicles are, how many are free, what the battery level is. Many cities now require a GBFS feed as a permit condition, which is why scooter availability shows up in third-party apps at all.

There's a third standard most riders never hear about, aimed at regulators rather than at you. The Mobility Data Specification was built so cities could receive and audit operator data — where vehicles are deployed, where trips start and end, whether a company is meeting its permit obligations — and issue rules back, like a geofence that says no parking here. It's the reason a scooter app can suddenly refuse to end your ride in a plaza. That standard is also why scooter availability appears in trip planners at all: cities made publishing a feed a condition of operating, and the public data fell out as a byproduct.

Then there's the part that isn't standardized in any comparable way: buying the thing.

Layer	What it does	How mature
Static schedules	Routes, stops, timetables	Solved. Open standard, near-universal
Realtime positions and predictions	Where the bus is, when it'll arrive	Widely available, quality varies by agency
Shared vehicle availability	Live bikes and scooters near you	Common where cities mandate feeds
Routing across modes	Stitching walk, ride, and transit into one plan	Good, and mostly the reason people open the app
Deep links to another app	Hands you off to the operator to unlock	Works, but breaks the single-app promise
In-app booking and payment	One tap, one charge, one receipt	Fragmented. The actual bottleneck
Cross-operator refunds and support	Someone accountable when a trip fails	Largely unsolved

Read that table top to bottom and the pattern is obvious. Everything that could be solved by publishing data got solved. Everything that requires two companies to share money and liability did not.

Payment is where the dream dies

A trip planner is a read operation. It needs information, and information is cheap to give away — agencies benefit when more people can find the bus. A booking is a write operation involving a fare, a customer relationship, a refund policy, and a question about who's responsible if the vehicle isn't there.

Operators are not enthusiastic about that. The customer relationship is the asset. An aggregator that owns checkout owns the rider, sets the terms, and can eventually squeeze the operator's margin. So companies build just enough integration to appear in the aggregator and no more — usually a deep link that boots you into their own app to actually pay.

Which means the experience most people get is: plan in one app, unlock in another, and hold four separate accounts with four stored cards. It works. It is not the seamless thing anyone promised.

Liability is the quieter blocker. Suppose you buy a three-leg trip in one app and the middle leg collapses — the bike station is empty, the connecting bus is cancelled, the scooter won't unlock. Who refunds you, who reroutes you, and who eats the cost of the taxi you now need? In a single-operator trip that's answerable. Across three companies with three sets of terms it becomes a contract negotiation nobody wants to have for a fare worth a few dollars. Most aggregators solved it by declining to sell the trip at all, which is why they hand you off with a deep link and keep the liability where it started.

The workaround that's genuinely spreading isn't an app at all. It's account-based ticketing, where the fare logic lives on the agency's servers instead of on a card or in an app. You tap a contactless bank card or a phone at the reader, the back end figures out what you owe, and it applies fare capping automatically — after enough taps in a day or a week, the rest are free. No pass to pre-purchase, no fare to calculate, nothing to know in advance.

That change does more for the average commuter than any bundled subscription ever did, and it required zero behavior change. You just tap what's already in your pocket.

The subscription bundle was a bad idea

This is the part of the MaaS story that gets soft-pedaled, so let's be direct: the flagship concept — pay a flat monthly fee, get a mixed allowance across modes — mostly failed, and it failed for reasons that were predictable.

Adverse selection is the first problem. Who buys a mobility bundle? People who travel a lot. A bundle priced for average use gets bought disproportionately by heavy users, so the operator loses money per subscriber or has to price it high enough that casual users see no value. Insurance companies have known this for a century.

Second, transit is already cheap in most places, and fare capping made it cheaper without a middleman. If a week of unlimited bus and rail costs less than a couple of rideshare trips, a bundle's headline value has to come from the expensive modes — and those are exactly the ones nobody wants to give away at a flat rate.

Third, and most damning, nobody was asking for it. People don't have a mobility budgeting problem. They have a "will this specific trip work right now" problem. Solving the second one is a routing and reliability job. The bundle was an answer to a question commuters never posed.

The useful way to judge any of these apps is not how many modes it lists. It's whether it tells you the truth about the next departure and whether it lets you pay without a detour. Everything else is a feature list.

What actually changed about commuting

Set aside the failed business models and something real did shift, mostly in how people make decisions in the ten seconds before they leave.

Waiting became optional. Before realtime arrivals, showing up at a stop meant committing to an unknown wait. Now you leave when the app says to leave. That's a small thing that changes the felt experience of transit more than most capital projects do, because unpredictable waiting is what people hate about buses — not the buses.

Transfers stopped being scary. A trip involving two unfamiliar routes used to require homework. Now it's a legible sequence with a countdown. The practical effect is that people take trips they previously wouldn't attempt, particularly off-peak and outside their usual corridor.

Mode choice got fluid. The interesting behavior isn't people abandoning cars — it's people who no longer have a default. They check, then choose. Rain and a tight schedule means rideshare. Nice day and a mile means a scooter. Rush hour means the train.

The first and last mile got filled in. Shared bikes and scooters made stations useful from farther away. A stop that was a fifteen-minute walk was effectively out of range; the same stop is a five-minute ride, which quietly expands the catchment area of existing infrastructure without laying a single new rail.

And a cost that's easy to miss: the people who most need reliable transit information are the least likely to have an unlimited data plan and a current phone. Realtime information delivered exclusively through apps redistributes convenience toward people who already had options. Agencies that kept their SMS arrival lines, station signage, and phone support running understood this. Ones that treated the app as a replacement rather than an addition made service worse for a slice of their riders while their metrics looked great.

Picking one and moving on

You need at most two apps, and the choice isn't complicated.

Start with your regional transit agency's official app if it has a decent one, because it's the only source that gets fare products and service disruptions first-hand. Add a general maps app for cross-mode planning and unfamiliar trips. Install individual operator apps only for the specific bike or scooter service you actually use in your neighborhood, and delete the rest.

Then check one thing: whether your local system takes a contactless bank card or phone tap directly at the reader, and whether it caps fares over a day or week. If it does, stop buying passes and stop thinking about it. If it doesn't yet, that's the single upgrade worth asking your agency about, and it'll do more for your commute than any app on the store.