Choose a Target Rider and Design the MVP for a City Bike Rental App

Design a mobile app that lets people rent bicycles. Choose who it serves first, which of their problems it solves, what the first version does, and how you would measure success. ```hint The fleet is part of the product Whether a rider finds a working bike nearby and can leave it legally at the destination shapes the experience more than any screen does. Pick a rider whose trips you can serve reliably, and design around that whole trip. ``` ### Clarifying Questions - Are we a new entrant with our own fleet, or adding bike rental as a mode inside an existing app such as Uber's? - Is the rental for short trips around the city (unlock, ride, drop off), for longer rentals by the day or month, or both? - Are bikes returned to fixed stations or left anywhere inside allowed zones, and are they pedal bikes, e-bikes or both? - Which cities come first, and is the goal rider growth, frequent use, or profit per bike? ### What a Strong Answer Covers - A chosen rider segment (commuters, students, tourists, couriers) with reasons tied to how often they ride and to the goal. - Pain points across the whole trip: finding a working bike, unlocking it, riding safely, parking and paying. - A first version that closes the find, unlock, ride, park and pay loop reliably, plus the operations behind it such as rebalancing, repair and theft prevention. - Pricing choices such as pay per ride versus passes, and their effect on habit and revenue. - A north-star metric paired with fleet measures like rides per bike per day, and guardrails for parking complaints, damage and safety. ### Follow-up Questions - Every morning bikes pile up downtown and run out in residential areas. What do you change in the app and in operations? - The city threatens to cut your permit over bikes blocking sidewalks. How does the product respond? - How would the design change if the main users were tourists instead of locals?