The Mobile Landscape
What Makes Mobile Different
Mobile product management shares fundamentals with web or desktop PM, but the constraints are tighter and the stakes higher. Users install an app deliberately and expect a fast, reliable, and intuitive experience. A crash on mobile feels more personal than a broken web page.
Mobile-Specific Constraints
| Constraint | Implication |
|---|---|
| Screen size | Information density must be lower; navigation must be thumb-friendly. |
| Battery & data | Background processes, sync frequency, and media loading need careful trade-offs. |
| Offline mode | Apps must handle intermittent connectivity gracefully — cache reads, queue writes. |
| App store gate | Every update goes through review. Hotfixes take hours to days. |
| Install friction | Users must discover, download, and grant permissions before the first interaction. |
| Device fragmentation | 24k+ Android device models; 5 iOS screen sizes in active use. |
Platform Ecosystems
The two dominant platforms have different governance philosophies:
- Apple (iOS): Closed ecosystem, strict guidelines, high-quality bar, longer review cycles, higher user willingness to pay.
- Google (Android): Open ecosystem, more permissive guidelines, side-loading possible, larger global reach, lower average revenue per user.
A mobile PM must understand both ecosystems deeply enough to make trade-offs about feature scope, release timing, and compliance.
User Behaviour Patterns
Mobile sessions are short — median session length is under 3 minutes. Users open an app with a specific intent and expect friction-free completion. This changes how you prioritise: completion rate and time-to-value matter more than feature breadth.
The Mobile PM Mindset
Every decision — what to build, when to release, which OS to target first — is amplified by the app store dynamic. A bad 1.0 launch means 1-star reviews that take months to recover from. Mobile PMs learn to think in terms of versions, not features, and to treat the app store listing as a product surface in its own right.
Next: Chapter 2 — Platform Strategy: Native vs Cross-Platform