Why the shift from MaaS to MaaF?

Mobility as a Feature — MaaF — describes what happens when mobility stops being a destination app and becomes a capability inside something else: a banking app that sells a train ticket, a municipal services portal that arranges accessible transport, an employer’s system that books the commute.

The shift is partly an admission. Standalone MaaS apps have struggled to win the daily habit that mapping services and public transport apps already hold. Embedding mobility where people already are is a lower-friction route to the same integration.

For a foundation working on open infrastructure, MaaF raises the stakes rather than lowering them. If mobility is going to be embedded across many surfaces, the layer underneath has to be genuinely open — otherwise every new surface is negotiated one commercial agreement at a time, and the traveller’s options quietly narrow to whoever signed the deal.