Build a mobile app.

Take a mobile idea from sketch to store. Plan the screens and features in Manager, hand the build to coding agents, and track every release through to ship.

Why build it in Manager?

One plan for parallel builds

Screens and features become a prioritized backlog coding agents can pick up several at a time.

Specs your agents follow

Every screen carries acceptance criteria and design notes, so agents build the right thing.

Always release-ready

Progress, decisions, and docs stay current, so you always know what is in the next build.

The workflow.

  1. Map the screens and flows

    Capture each screen and user flow as goals and tickets with acceptance criteria.

    Say to your agentManager: Interview me about the app and create a goal for each screen and flow, with acceptance criteria.

  2. Connect your coding agent

    Wire a coding agent (Claude Code, Cursor, …) to Manager over MCP.

  3. Build features in parallel

    Agents claim tickets from the backlog and implement several screens at once.

    Say to your agentManager: Take the next ready screen from the backlog, start work and build it to spec.

  4. Track builds and fixes

    Log bugs and QA as tickets; Manager keeps the next release in focus.

    Say to your agentManager: File these TestFlight crash reports as bugs for the next release milestone.

  5. Ship to the stores

    Review completed work in Manager and release, with a full record behind it.

    Say to your agentManager: Check that everything in the release milestone is done, then close it.

From sketch to shipped app.

Manager keeps the plan, the backlog, and the docs in one place, so the app you ship is the app you set out to build.

Get early access