Product Design: Build an App That Gets People to Read More Often

Design a new app whose goal is to get people to read more. Who would you build it for, what would it do, and how would you know it is working? ```hint Start from why people do not read Wanting to read more stalls for different reasons: no time, no idea what to read next, losing focus, or no access to books. Choose the group whose obstacle is sharpest before you think about features. ``` ### Clarifying Questions - What counts as reading here: books only, or also long articles, newsletters and audiobooks? - Should I target a particular audience, such as children building literacy, students, or adults who used to read and stopped? - Is this a standalone app, or can it launch inside an existing product that already has an audience? - Should success be measured in time spent reading, books finished, or a business outcome such as paid subscriptions? ### What a Strong Answer Covers - A precise definition of "read more" and a chosen reader segment, with the reason for choosing it - The real obstacles that segment faces, ranked, rather than a list of generic features - A focused first version with prioritized features, plus a sketch of the main components needed to build it - A success metric that reflects actual reading, with guardrails against shallow engagement such as streak-chasing - How the app reaches its first users and keeps the habit going, and the main risks ### Follow-up Questions - Daily opens go up but books finished stay flat. What might be happening, and what would you change? - Where would the books or articles come from, and how does that choice affect cost and what you can offer? - Which parts of the first version would you build in-house, and which would you license or buy?