Uber’s product chief on hotels, robotaxis, and why the company doesn’t want to be “everything for everyone”

Uber’s Product Expansion: What It Means for Developers

Uber’s chief product officer Sachin Kansal recently laid out a vision that extends well beyond ride-hailing and food delivery. The company is now actively building a travel vertical — hotel bookings via Expedia, boat rentals, and a “shop for me” concierge — while simultaneously investing in autonomous vehicle data infrastructure and experimenting with financial services for drivers and merchants. For developers and builders, these moves signal a platform that is deepening its API surface, hedging against future competitive dynamics, and quietly assembling a data moat that could reshape how third parties interact with Uber’s ecosystem.

The headline product news — hotels, boat rentals, and expanded shopping — might seem like consumer-facing features. But the strategic underpinnings matter for anyone building on top of Uber’s APIs or considering integrating with its platform. Kansal explicitly framed travel as “the third leg of the stool,” after rides and eats. That means Uber is formalizing a multi-modal trip planning layer that developers can tap into. Hotel bookings, for instance, aren’t just a new tab in the app; they represent a new API category that could eventually support itinerary bundling, loyalty credit redemption, and cross-sell logic between transportation and accommodation.

AV Labs: A Data Play with Strategic Hedges

Perhaps the most consequential move for builders in the autonomous vehicle space is Uber’s creation of AV Labs, a six-month-old business unit that operates a fleet of sensor-equipped vehicles separate from the regular driver network. The unit’s stated purpose is to collect ever-larger amounts of driving data to strengthen relationships with AV partners — several of which Uber holds equity in. But the implication is clear: Uber is building its own data pipeline for autonomous driving, independent of any single partner.

For developers in the AV and robotics space, this is a significant signal. Data labeling is notoriously expensive and labor-intensive. Uber is already using its driver network as a side hustle for labeling, which means it can scale data annotation at a fraction of the cost of traditional approaches. The AV Labs fleet adds a proprietary data collection layer that could eventually power everything from perception model training to simulation scenario generation. That data could also become a product — licensed to partners or used to benchmark third-party AV systems.

The competitive tension with Waymo is particularly instructive. Uber partners with Waymo in some markets while competing in others. Owning the data layer gives Uber leverage and optionality, especially as robotaxi deployment accelerates. For builders evaluating which AV platform to integrate with, Uber’s data strategy suggests a dual-track approach: partner today, but maintain the capability to build or pivot tomorrow. Developers should watch how Uber exposes AV-related data — if at all — through developer APIs in the coming quarters.

When assessing the cost of building similar data infrastructure, you can use an LLM API cost calculator to model the computational expense of processing sensor data at scale, though sensor costs and labeling labor remain separate line items. The economics of data moats are central to understanding why Uber is making this bet.

Financial Services and the Platform Economy

Kansal was measured when discussing financial services, but the details reveal a platform that is quietly embedding payment and credit infrastructure. The Uber Pro card — a debit card for drivers and couriers — already moves earnings onto a proprietary card. Uber credits serve as a closed-loop currency for consumers, and the company is experimenting with merchant-side financial products in select markets.

For developers building on Uber’s platform, this creates both opportunity and constraint. On one hand, the Uber credits system and Pro card represent new integration points — you could build tools that help merchants accept Uber credits or help drivers optimize earnings transfers. On the other hand, Uber is deliberately not building its own buy now, pay later product, preferring to partner with incumbents. That means developers who build fintech layers on top of Uber should expect partnerships rather than in-house solutions for credit and lending.

Kansal’s comment that Uber is “not trying to be everything for everyone” is telling. The company is cherry-picking financial services that directly reinforce its core ride-and-delivery flywheel. Driver earnings cards and consumer credits that can be redeemed for rides create stickiness. Broader banking or lending products are left to experts. For fintech developers, this means Uber’s API surface will likely remain focused on transaction data, loyalty balances, and partner integrations — not full-stack banking.

Travel as the Third Leg: APIs and Multi-Modal Integration

The travel expansion is more than a list of features; it’s a redefinition of Uber’s platform scope. With 1.5 billion trips per year occurring outside a user’s home city, travel is already a natural use case. Adding hotel bookings, boat rentals, and store shopping converts Uber from a point-to-point transportation app into a trip orchestration layer.

For developers, this means Uber’s API suite could soon support multi-step itineraries that combine rides, food delivery, hotel reservations, and local shopping — all potentially linked by Uber credits and membership perks. The partnership with Expedia for hotel inventory suggests Uber is not building its own travel supply chain but rather aggregating through partners. Developers building travel or logistics applications should consider whether Uber’s API becomes a distribution channel for their own services, or whether it competes for the same transaction.

The “shop for me” feature is particularly interesting. It allows users to order from any local store, even if that store isn’t on Uber Eats, by using a concierge model. This is essentially a last-mile shopping API that could scale beyond food. Developers building local commerce platforms should watch how Uber handles catalog integration and fulfillment — it may open up new ways to reach customers without traditional delivery partnerships.

For a comparative view of how Uber’s platform pricing stacks up against other API-driven ecosystems, the LLM API pricing reference provides a useful framework for thinking about cost structures — even though Uber’s APIs are not LLM-based, the principles of metered usage, tiered access, and partner revenue sharing are directly analogous.

AI Under the Hood: Practical Improvements for Riders and Drivers

Kansal mentioned that AI is starting to show up “in ways riders and drivers will actually notice.” While the interview did not detail specific AI features, the broader context points to several likely applications. The AV Labs data pipeline will improve routing and ETA prediction for human-driven rides as well. Personalization of food recommendations, dynamic pricing models, and fraud detection all benefit from the driving data Uber is now systematically collecting.

For developers building on Uber’s APIs, improved AI means better quality of service: more accurate ETAs, smarter dispatch, and potentially lower cancellations. It also means that Uber’s platform becomes more opaque — the algorithms that determine pricing, matching, and routing are increasingly complex. Builders should consider how AI-driven decisions affect their own applications, especially if they rely on deterministic behavior from Uber’s systems.

The data labeling program for drivers also has a developer angle. Drivers can earn extra money labeling data, which feeds Uber’s AV ambitions. For developers working on labeling tools or data pipelines, Uber’s model of using gig workers for annotation is both a validation of the approach and a competitive challenge — Uber can scale labeling at marginal cost using its own workforce. Any startup building labeling SaaS should factor in this kind of vertical integration.

Conclusion: Platform Risk and Optionality for Builders

Uber’s product chief has drawn a clear line: the company will expand into travel, build a proprietary data infrastructure for autonomy, and selectively offer financial services, but it will not try to be an everything app. For developers, this is a mixed signal. On one hand, Uber is creating more integration points — travel APIs, data services, and payment rails. On the other hand, each expansion increases platform risk. The more Uber controls the data layer, the harder it is for third parties to build competitive services on top of it.

The key takeaway for builders is to evaluate Uber’s platform as a strategic partner, not just a distribution channel. The AV Labs data effort will likely produce valuable datasets or benchmarks that developers can license — or compete with. The travel vertical will create new opportunities for cross-promotion and itinerary APIs. The financial services experiments suggest a focused, not sprawling, fintech strategy. Developers who understand where Uber is making long-term bets — data, travel, and closed-loop payments — can position themselves to complement rather than compete with the platform.

Ultimately, Uber is hedging against a future where autonomous vehicles and super-app dynamics reshape the transportation industry. Its product strategy reflects a desire to own the data and the loyalty loop, while leaving specialized functions to partners. For the developer community, the smartest play is to build for modularity — integrate with Uber where it offers clear value, but maintain the ability to route around it when competitive dynamics shift.

Source: TechCrunch. Details as reported; verify specifics at the source.