Defend a mobile OS preference and design a product that exploits that platform

An interviewer asks whether you prefer iOS or Android, then asks you to design a product of your own choosing for the platform you picked. Answer both halves: defend your preference, then design a product that builds on it. ### Clarifying Questions - Should I judge the platforms as an everyday user, or as a product manager deciding where to build? - Can the product be a built-in system feature, or should it be an app that anyone can install from the store? - Is there a goal I should design toward, such as reaching new users, engagement or revenue, or is that my choice too? - Should I target a particular country, or a time frame for the first release? ### Part 1 — Pick a Platform and Defend It State which mobile operating system you prefer and why, both as someone who uses it daily and as a product manager who would build on it. Acknowledge what the other platform does better. ```hint Separate taste from leverage Liking how a platform looks is taste. Look for what each platform lets a product do, or lets it reach, that the other does not, so your reason carries into Part 2. ``` #### What This Part Should Cover - A clear choice backed by concrete platform traits rather than brand loyalty - A fair account of the other platform's strengths - A link from the preference to the kind of product it makes possible ### Part 2 — Design a Product for That Platform Choose a product and design it: the goal, the users it serves, their most important problems, the features of a first release, and how you would measure success. The design should depend on something your chosen platform makes possible or does better. ```hint Let the platform point to the users Ask which group of people your platform reaches especially well, or which system capability it opens to app makers, and look for an unmet need there before listing features. ``` #### What This Part Should Cover - A goal and a deliberately chosen user segment with ranked pain points - A small first release whose features use the platform's capabilities, with what was cut and why - Success metrics with guardrails, and the main risks ### What a Strong Answer Covers - A consistent thread from the platform preference to the product choice - Platform capabilities and store policies described accurately, including limits on what an installed app may do - Clear prioritization between the first release and later ones - Measurable success criteria and a plan for privacy, safety and trust risks ### Follow-up Questions - How would your design change if you had to build it on the other platform? - If store policy blocked your most important feature, what would you ship instead? - What result from the first release would make you stop investing in this product?