Pocket · Product sense · Entry · 45 to 60 minutes

How should Pocket improve first-session retention?

Pocket is an app that lets people save articles and web pages to read later across devices. Answer this product management case and get it graded line by line against a weighted rubric.

product sense
prioritization
user empathy
metrics
experimentation

The situation

Pocket's mobile PM is reviewing a worrying pattern. Many people install the app, create an account, and complete their first session, but too few return in the following days. Pocket is a small team, so the next release can only tackle a narrow part of the new-user experience. The team already knows the first session has three sensitive moments: teaching people what Pocket is for, asking Android users for notification permission, and getting the home screen to load reliably before the user has saved much content. Feedback is mixed. Some users seem unclear about cross-device use, some dismiss prompts too quickly, and some lose trust when the app feels slow early on. Leadership wants a recommendation now because retention matters more than adding new features this quarter. Your job is to propose what Pocket should change first in the first-session flow, why that is the right bet, and how the team should measure whether it worked.

What to produce

Write a 1 page product recommendation memo, 500 to 700 words.

Your answer must

State the main retention problem in the first-time mobile experience and the specific user behavior you want to improve.
List 2 to 3 hypotheses for why new users do not return, using the onboarding, permission, and early performance moments in the scenario.
Recommend the highest-priority change for the next release and one lower-priority follow-up, with clear tradeoffs.
Explain how you would handle notification permission timing and whether Pocket should show any explanation before the system prompt.
Define a primary success metric, 2 to 3 supporting metrics or guardrails, and a simple test or instrumentation plan.

Constraints

Assume the team can ship only one medium engineering change and one lightweight UX change in the next 6 weeks.
You cannot change Android system permission rules, only when and how Pocket asks.
Do not redesign Pocket's core save and read later experience or add major new features.

Format

Use short sections such as problem, hypotheses, recommendation, metrics, and risks.

How Pocket actually played it

A first time user teardown of Pocket that pulls out six retention lessons across onboarding, permission prompts and loading speed. Short, concrete and easy to compare with your own product.

Ask for notification permission at a moment of delight, not at launch
Show your own explanation before the system permission prompt
Fix early latency before polishing features

Built from Pocket App: 6 lessons to improve Retention by Tear Them Down.