2026 is being pitched as the year every ride-hailing app becomes a mobility superapp — transit, scooters, bikes, all bundled in. For most challengers, that's the wrong fight to pick.
The same pattern shows up everywhere a focused challenger has beaten a larger, more diversified incumbent: winning comes from identifying the one area of genuine comparative advantage and going all in on it, not from spreading across many fronts at once. It's the reason startups can beat incumbents in the first place — a larger, more diversified competitor structurally can't focus as sharply as a smaller one can, so a focused challenger can simply out-execute them in one lane. Trying to compete across rides, food, transit, scooters, and bikes simultaneously as a smaller player gives up the one real advantage a challenger has.
Rides and food delivery are the two categories with real scale — basket size, real margin, and the kind of habitual, repeat usage that builds a durable business. Everything else in the "mobility superapp" pitch is small by comparison. A major scooter operator's total revenue sits somewhere in the $1-1.5bn range; a major ride-hailing platform's GMV runs closer to $200bn. Scooters and bikes aren't a rounding error exactly, but they're nowhere near large enough to justify a challenger's limited product and engineering attention.
Transit integration is the category that sounds most appealing and delivers the least. It's not simply a "nobody's built it well yet" problem — it's structural. City transit agencies mostly run on genuinely old, fragile IT systems: databases and code that can be two or three decades old, maintained by under-resourced IT teams, that don't integrate cleanly with anything modern. A handful of cities (Singapore, Dubai) have modern enough infrastructure to make integration realistic, but even there it's largely beside the point — heavy transit users are typically on flat monthly subscriptions (Germany's nationwide transit pass, for example, runs a flat rate for unlimited use) and simply never open a ride-hailing app for their daily commute at all. There isn't much revenue in it for a ride-hailing platform even where the integration problem is technically solvable.
China's 2016 bike-share boom is worth remembering here. For a period, the entire industry genuinely believed shared bicycles were the future of urban mobility — the hype was total. It wasn't true. The money was never really there, and most of that capital and attention evaporated without building anything durable. The pattern repeats every time a new "everything app" category gets hyped: the excitement outruns the actual unit economics.
Uber's own history is the best case for bundling done right, precisely because it wasn't simultaneous. Rides scaled to roughly $10bn in GMV entirely on its own first. Only once that business was genuinely dominant did a second vertical — food delivery — get added. One adjacent category, added sequentially, after the first was already won. That sequencing is the model worth copying, not the "add everything at once" version most operators are chasing in 2026.
For a smaller, regional challenger, the exception would be a market where rides alone genuinely can't reach defensible scale — in which case bundling stops being optional and becomes closer to forced. That's a narrow case, not the default one, and it's worth being honest with yourself about which situation you're actually in before spending engineering time on a second vertical.
A short working call — I'll tell you if you've actually won the first fight yet.
Book a working call