Decide whether food delivery and ride-hailing belong in one Uber app

Uber offers both ride-hailing and food delivery. Should Uber Eats be its own app, or should food delivery live inside the main Uber app that people use to book rides? Make a recommendation, then say which metrics you would monitor to tell whether it is working. ```hint Who opens which app, and when Compare who uses each service, how often and in what frame of mind. Then think about the people doing the driving and delivering, and the restaurants, not only the customers. ``` ### Clarifying Questions - Is this a decision for a new launch, or are we reconsidering a delivery app that already sits alongside the rides app? - Is the main goal growth in delivery orders, more people using both services, or lower cost to build and market two products? - Does the decision cover the driver and courier app and the restaurant tools, or only the apps customers use? ### What a Strong Answer Covers - The goal behind the decision, and how rides and delivery customers differ in intent, frequency and overlap - The real benefits of each option: focus, habit and app store presence for a separate app versus cross-selling, one account and one membership in a combined app - Effects on drivers, couriers and restaurants, and on engineering and marketing cost - A clear recommendation, possibly a hybrid, with the evidence that would reverse it - Metrics for both businesses, including guardrails on rides, and a way to test the change ### Follow-up Questions - If a combined app raises delivery orders but booking a ride takes longer, what would you do? - How would you test a combined experience without putting the ride business at risk? - Would your answer change in a new market where Uber has rides but no delivery yet?