You’re a PM at CodePilot, a cloud IDE and code review platform (think GitHub + VS Code in the browser) with 12M registered developers and 2.4M weekly active users (WAU). CodePilot’s revenue is primarily B2B SaaS: $25–$45/seat/month for teams, plus enterprise add-ons (SSO, audit logs, compliance exports). The desktop web app is the core experience, but mobile usage is growing fast: 31% of WAU open CodePilot on iOS/Android at least once a week, mainly to review PRs, triage issues, and monitor CI.
CodePilot’s desktop app has a “Git pane” (left sidebar) that covers: current branch, uncommitted changes, file diffs, staging/unstaging, commit message, push/pull, and quick actions like stash and checkout. It’s heavily used: 58% of desktop sessions interact with it.
Mobile developer workflows are increasingly common due to remote work and on-call rotations. Competitors:
CodePilot’s differentiation is tight IDE + repo integration and a “single surface” for code, review, and CI. Leadership believes bringing Git workflows to mobile can reduce time-to-respond during incidents and increase seat stickiness in enterprise accounts.
| Persona | Share of mobile WAU | Primary mobile context | Top needs | Top fears |
|---|---|---|---|---|
| On-call Engineer (Asha) | 22% | Incident response, commuting, late night | Quickly inspect diffs, revert/patch, confirm what changed | Making a risky Git action on a phone |
| Reviewer/Tech Lead (Miguel) | 34% | Between meetings | See what changed, leave feedback, sanity-check | Losing context / missing files |
| Indie Dev (Rina) | 18% | Side projects | Make small edits, commit, push | Complex UI, accidental pushes |
| Student/Learner (Noah) | 26% | Learning Git | Understand status, stage/commit basics | Confusion, destructive commands |
Mobile sessions are frequent but shallow:
Enterprise customers specifically requested: “Let on-call engineers quickly verify and ship a one-line hotfix from mobile—with guardrails.”
However, there’s risk: internal data shows that on desktop, 0.7% of Git actions trigger a recovery flow (revert/reset/stash recovery). On mobile, leadership wants that rate to not exceed 0.9% after launch.
Design how the Git pane should look and behave on mobile—not a 1:1 port from desktop.
In your answer, cover:
We’re looking for a structured approach that starts from user needs, proposes a mobile-native design, prioritizes an MVP, and defines measurable success criteria with clear guardrails.