Project Background
Meta is preparing to launch a major update to the Instagram Reels composer on iOS and Android. The feature adds AI-assisted editing, a redesigned publish flow, and new media caching behavior intended to reduce creation time and increase publish completion. You are the mobile engineering lead partnering with a PM, EM, data scientist, and release manager across a 12-person team, and leadership wants the rollout started within 8 weeks because Reels creation is a top company priority this half.
Key Stakeholders
The Instagram Reels PM wants broad exposure quickly to capture engagement gains before the next planning review. The Mobile Infrastructure team is concerned the new caching layer could increase app crashes, startup latency, and memory usage on lower-end Android devices. The Integrity team wants confidence that the new publish flow does not weaken abuse checks. The on-call mobile engineering manager wants a conservative rollout with clear rollback triggers to avoid a high-severity incident.
Constraints
- Timeline: 8 weeks from code freeze to 100% rollout
- Team: 6 mobile engineers, 2 backend engineers, 1 PM, 1 data scientist, 1 QA engineer, 1 release manager
- Budget: no additional headcount; only $60,000 available for external device lab coverage
- Dependencies: App Store and Google Play review cycles, Mobile Infra sign-off, and instrumentation updates in Scuba dashboards
- Technical constraint: the feature must support the current Instagram app version plus the previous 2 app versions still active in the field
Complications
- Existing crash reporting is delayed by up to 45 minutes for some Android cohorts, limiting how fast regressions can be detected.
- A parallel Instagram Home ranking experiment is scheduled during the same month and may change Reels creation traffic patterns.
- One staff Android engineer who owns the media pipeline is only available 25% of the time due to a P0 reliability effort.
Your Task
- Define a phased rollout plan, including exposure percentages, gates, and decision owners.
- Specify the monitoring strategy and regression signals you would use to catch issues quickly.
- Propose rollback criteria and an operational response plan for launch week.
- Identify the main cross-functional risks and how you would mitigate them.
- Explain trade-offs between rollout speed, learning speed, and user risk.
