Designing a city sightseeing app that keeps working without a data connection

Design an app that helps people tour a city in offline mode. Decide who it is for and what problem it solves for them, define the core experience and what the app needs to work offline, prioritize a first version, and explain how you would measure success. ```hint Split before and during Separate what a traveler can fetch while still connected from what they will need once the connection is gone, and ask which of those needs comes up most often during a day of sightseeing. ``` ### Clarifying Questions - Does offline mean no data connection for the whole trip, or patchy connectivity where the app can sync whenever Wi-Fi is available? - Is this a standalone app or a mode inside an existing maps or travel product, and is there a business goal beyond adoption? - Should it launch in one city or cover many cities from the start? - How much phone storage and battery drain is acceptable for a full day out? ### What a Strong Answer Covers - A stated reading of "offline mode" and a goal for the product - Traveler segments compared, with one chosen and the reason for it - Needs across the trip, from planning to the end of a day out, ranked by how much they hurt without a connection - A first version scoped by what must work offline, with explicit prioritization criteria - Success metrics with guardrails, plus offline-specific constraints (storage, battery, content freshness) and how the design handles them ### Follow-up Questions - How would you make money from the app without weakening the offline experience? - What happens when a traveler arrives in the city without having downloaded anything? - How would the design change for a city whose signs and menus use a script the traveler cannot read?