Mobile App Product Management

A clear view of your app's health, release trains through both stores, OS support decisions, push permission, ratings and offline behaviour, and the routines that keep a mobile product shipping safely.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Mobile App Product Management, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

203

Starter tasks

🧩 Product Management

Mobile App Product Management

Managing a mobile app product, including app store releases, platform differences, push notifications, ratings and offline behaviour.

  1. Mobile app health baseline on one page
  2. Developer accounts, signing keys and access audit
  3. Supported devices and OS versions matrix
  4. Minimum OS version support policy
  5. Release pipeline map from branch cut to store
  6. Crash-free rate target and alerting
  7. Store privacy labels and data safety form audit
  8. Platform parity register across iOS, Android and web
  9. App version adoption dashboard
  10. Weekly mobile release train
  11. Pre-submission release checklist
  12. Phased rollout watch for every store release
  13. Weekly crash and ANR triage
  14. Store review reading and reply routine
  15. Monthly ratings and review themes report
  16. Monthly version adoption and upgrade review
  17. Annual OS release readiness cycle
  18. Quarterly store policy and guideline watch
  19. Third-party SDK inventory and review
  20. Push token and delivery health check
  21. App store review guidelines working knowledge
  22. Why mobile releases differ from web releases
  23. Mobile performance metrics a product manager should read
  24. Human Interface Guidelines and Material Design conventions
  25. Runtime permissions on iOS and Android
  26. Offline-first and sync basics for product decisions
  27. Tracking consent and mobile privacy frameworks
  28. Native or cross-platform framework decision
  29. Push permission request timing and pre-prompt
  30. Offline behaviour spec for the core flows
  31. App download size reduction
  32. Cold start time reduction
  33. Forced upgrade and minimum version mechanism
  34. Deep links and universal links coverage
  35. In-app rating prompt placement
  36. Mobile accessibility audit with screen readers and large text
  37. In-app account deletion flow
  38. First submission of a new app to both stores
  39. App store rejection response plan
  40. Emergency hotfix and expedited review drill
  41. Major redesign release on mobile
  42. Store editorial featuring nomination
  43. Engineer stepping into mobile product ownership
  44. Web-first team shipping its first mobile app
  45. Taking over an inherited app with poor ratings
  46. Small team running an app with one mobile engineer
  47. Building for low-end devices and patchy networks
  48. Tablet, foldable and large-screen layouts
  49. Widgets, watch apps and other platform surfaces
  50. Server-driven screens to ship without a store release

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Mobile app health baseline on one page

Before changing anything, a mobile product manager needs the handful of numbers that describe the app today: active users by platform, crash-free users, store rating per platform, share of users on the latest version and cold start time. Pulling them onto one page from the store consoles, the crash tool and analytics gives every later decision a starting point and exposes any number nobody can currently find.

First tasks

  • Open both store consoles and note this month's active devices per platform
  • Copy the 30-day crash-free users figure from the crash reporting tool
  • Record each store's current rating and the number of ratings
  • Ask the agent to draft the one-page baseline from the collected figures
  • List the missing metrics and name an owner for each

Developer accounts, signing keys and access audit

Apps are often published from a developer account opened years ago by someone who has since left, and losing control of an Android signing key or an Apple account can stop updates entirely. An audit of who owns each store account, where signing keys and certificates live and who can submit builds turns a single point of failure into a documented, shared arrangement.

First tasks

  • Write down who holds the account owner role in each store console
  • Find where the Android upload key and the iOS distribution certificate are stored
  • Remove console access for anyone who has left or no longer needs it
  • Record the expiry date of every certificate and the push key
  • Review console access and certificate expiry dates @recurring(yearly)

Supported devices and OS versions matrix

Bugs on mobile cluster on particular devices and OS versions, and testing everything is impossible. A matrix of the devices and OS versions your users actually run, weighted by share, tells QA what to test on, tells engineering which old versions cost the most and tells support what is officially supported.

First tasks

  • Export OS version share for the last 90 days from analytics
  • List the top 15 Android device models by active users
  • Agree three test tiers with QA and engineering
  • Refresh the matrix with the latest OS and device share @recurring(quarterly)

Make it yours.

Install Mobile App Product Management, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.