Duolingo · Execution · Mid · 45 to 60 minutes

Should Stories come to Android now?

Duolingo is a language learning platform with mobile apps and web lessons used by people around the world. Answer this product management case and get it graded line by line against a weighted rubric.

prioritization
execution planning
metrics
experimentation
stakeholder judgment

The situation

You are a PM in Duolingo's learning experience area. Stories, short interactive lessons that combine reading, listening, and comprehension questions, launched on web in 2017 and recently became available on iPhone. Now leadership wants a recommendation on whether Android should be the next step, and if so, how to ship it. This is not a simple port. Many of the lesson elements used in Stories do not exist yet in the Android app, Stories are only available for some language courses, and Android serves more than half of Duolingo learners across a wide range of devices. Android engineering time is limited, and other teams also want roadmap space. The team cares most about whether the feature makes people learn more, not whether it simply exists on another platform. You need to propose a realistic plan for the next planning cycle that covers scope, rollout, and measurement, while avoiding a misleading read on impact caused by differences between learners in supported and unsupported courses. Assume you can partner with engineering, design, and data science.

What to produce

Write a 1 to 2 page product execution memo.

Your answer must

Define the user and business problem, including why Android parity may or may not matter now for Stories.
Recommend a clear launch decision and a first release scope, separating what must be in version one from what can wait.
Specify 2 to 4 success metrics, with a primary metric tied to active learning or time spent learning.
Describe an experiment and rollout plan, including how you would choose control or comparison groups and handle the fact that only some language courses support Stories.
Identify the top Android delivery risks and quality risks, and propose practical mitigations or launch gates.

Constraints

Use existing Stories content only for the initial launch, do not assume new stories or new language support.
The Android app does not yet have all the UI and lesson components Stories need, so full parity on day one may be unrealistic.
Your plan must protect app stability across a wide range of Android devices.
This recommendation is for the next planning cycle, not a long term platform rebuild.

Format

A strong memo uses sections for recommendation, rationale, version one scope, metrics, experiment design, and risks.

How Duolingo actually played it

Duolingo brought Stories to Android and saw a 3 percent increase in users actively learning, with those who have Stories spending 4.6 percent more time learning. The post shows how platform parity for a popular feature was prioritized and measured. A small but clear example of quantifying a feature expansion.

Platform parity can be a measurable growth lever.
Compare users with and without the feature to size impact.
Tie delivery to an engagement metric.

Built from Duolingo Stories: The journey to Android by Ming Zhang.