MaleusMaleus

Navigate the version workflow

A guided version moves through Design, Specifications and Development. The phase stepper in the topbar takes you back to any phase you have already passed.

In the appVersion detail
On this page

Every version follows a workflow. Which phases it has depends on the type you created. The topbar shows it next to the version number, as Guided or Direct.

The two workflows

TypePhases
GuidedDesign → Specifications → Development → Done
DirectDirect → Done

The step tabs sit in the header. Later steps stay locked until the current one is done.

What each phase is for

Design

Shape your app's frontend: its screens, its layout, its flow. No specs, no code yet. The preview runs on a mocked API so iterating stays fast.

Specifications

Define the internal software behind those screens: the backend, the data, the logic. This is the plan the agent will build from, and the cheapest place to correct anything that is off. You comment on whatever is off, then send the comments to the agent in one go. See Refine specifications with the agent.

Development

The agent builds your app from the design and the specifications. The workspace tabs on the right (Preview, Source code, Reviews, Database, Logs, Terminal) let you run it, inspect it, and capture feedback. The preview now points at the real API.

Done

The version is complete and moves to the Ready to Deploy card on the versions list, where you Promote it to a deployment target.

Direct (direct versions only)

A file workspace with live updates, driven straight from the code. No design and no specification phase.

The phase stepper

The stepper sits in the topbar, under the version identity: one connected segmented control, one cell per phase. The active phase fills its cell, the phases you can reach are clickable, the locked ones are greyed out.

Hovering a cell tells you what the phase is for, or why you cannot go there yet:

  • "Finish "{previous phase}" first to unlock." when you have not reached it.
  • "Available once the agent finishes the current phase." while the agent is working.

Clicking the version identity opens a popover with the same information laid out as a list, one row per phase, under its Workflow tab.

Moving forward

The chat carries the CTA that advances the version, and it appears once the agent has finished its turn and is waiting on you:

  • Move to {phase} on a guided version, for example Move to Specifications.
  • Mark as Done on the last phase, and on a direct version.

The CTA is hidden while the chat is read-only or the environment is not ready. Turn on Auto-pilot in the preview controls and the agent chains the phases itself, stopping at Development for your feedback.

Going back

Click any phase you have already passed. Going backwards adds a query parameter to the URL: ?openedStep=design-step or ?openedStep=spec-step, and clicking the current phase removes it. The URL is shareable: paste it to a teammate and they land on the same phase.

Going back is non-destructive. Your design assets, specs and generated code all live on the version, not on the phase, so returning to Specifications does not roll back the code the agent already wrote.