Plan the Iteration Roadmap

Background: Native [platform] app, post-launch. Inputs I have: [analytics
insights (12.2), crash priorities (12.1), review themes (12.4), and my
original deferred features (Section 1)]. Resources: [solo / team, time
available].

Use case: Synthesize all the post-launch signal into a prioritized
iteration roadmap for the next few releases.

Implementation details:
- Weigh fixes (crashes, top complaints) against growth (retention/
  conversion levers) against deferred features and tech debt
- Reuse a prioritization framework (RICE/MoSCoW from 1.6) but now scored
  with real data, not guesses
- Sequence into concrete releases with themes, respecting store-review
  cadence and the cost of shipping
- Reserve capacity for maintenance and the inevitable hotfix
- Name the one bet each release is making

Deliverable: A prioritized roadmap grouped into the next 2–3 releases,
each with a theme and its core bet, the data justification for the
ordering, and the maintenance/hotfix buffer.