Open Orbit

Workspaces

Understand how Orbit workspaces show different parts of one app, and why a page check does not replace a live test.

Orbit workspaces show different parts of the same app: its pages, stored information, server logic, and deployment.

A workspace is a view of the app, not a separate app. Use the view that answers your current question.

Each view answers a different question

WorkspaceQuestion it helps answer
ExploreWhich part of the app do I need to inspect?
MockupWhat pages do people see, and what does each page contain?
WorkflowWhat server logic runs after an action?
Data ModelWhat information does the app store, and how do records relate?
LaunchWhich environment contains the change people will use?

Orbit Agent lets you request a change in words. The workspaces help you inspect the parts that change affects.

One change can affect several views

Consider a repair request app. The app and names below are examples, not a built-in template.

Suppose customers need to select a repair category when they submit a request. That requirement has several parts:

  • The page needs a category control that a customer can use.
  • The data model needs a place to store the category with the request.
  • Any workflow that routes requests needs to use the selected category.
  • The customer-facing environment needs the tested change.

Mockup helps you inspect the control. Data Model helps you inspect the field. Workflow helps you inspect the routing logic.

These checks answer different questions. A category control on a page does not prove that the app saves the selected value.

A workspace is not an environment

A workspace describes the part of the app you inspect. An environment describes a separate copy of the app with its own address and state.

Launch distinguishes Sandbox, Review, and Production. Sandbox supports experiments. Review supports checks before release. Production is the live app customers use.

A change in a test environment does not reach Production until you deploy it there. Read Launch workspace for the deployment model.

Inspection and live tests provide different evidence

For the repair app, a complete test uses the form to submit a request with a category. The saved request must show that category after you reopen the app.

If the app routes requests by category, check the routing result separately. A saved category does not prove that the routing worked.

Repeat the main customer task at the Production address after deployment. A successful test at another address does not prove the result customers receive.

Use Review an app before launch for practical checks. For a page change, start with Edit a mockup.