Designing an Airport Passenger App and Its Revenue Model

Design a mobile app for an airport that earns money. Decide whom it serves and what it does for them, explain how it generates revenue, and say how you would judge whether it is succeeding. ```hint Earn the install before the revenue An app people open once or twice a year at a given airport has to earn its install before it can earn money. Find the traveler problem that justifies opening it, then ask which parties in the terminal would pay, and for what. ``` ### Clarifying Questions - Who is building the app: the airport operator, an airline, or an independent company that would need the airport's cooperation for gate, wait-time and shop data? - Is it for one specific airport, or meant to work across many airports? - Should it serve departing passengers only, or also arriving passengers, people meeting them, and airport staff? - Is revenue expected from launch, or is adoption the first goal with monetization following? ### What a Strong Answer Covers - A stated owner and goal, and a chosen traveler segment with the reason the others wait - Pain points along the airport journey (getting there, security, wayfinding, waiting, connections, arrival) that a phone app can actually address - A prioritized feature set in which the core utility stays free and drives adoption - A revenue model naming who pays (travelers, shops and restaurants, transport partners, advertisers) and how monetization avoids eroding trust or usage - Success metrics and guardrails spanning adoption, traveler value and revenue ### Follow-up Questions - Most travelers pass through a given airport only a few times a year. How would you get them to use the app, and would you build for one airport or many? - Airlines already have apps that show gates and boarding passes. Why would a traveler open the airport's app instead? - If concession revenue rises but app ratings fall after you add sponsored placements, what would you do?