# Understand the product lifecycle

An Orbit app moves through a repeating cycle: explore, shape, build, launch, and grow. What you learn after launch starts the next cycle.

## Explore the problem

Start with the user and the job. Keep the evidence, notes, and links that explain why the app should exist.

Do not start with every possible feature. Find the smallest result that one person can use and check.

## Shape the first version

Choose the pages, data, and actions required for that result. State what the first version will not include.

A clear scope helps you identify which assumption to check.

## Build the connected parts

Build the interface in **Mockup**, the stored information in **Data model**, and server actions in **Workflows**. These parts stay connected inside one app.

Use the preview as you work. Add test data that covers the normal path and one failure path.

## Check the deployment

Use **Launch** to check the deployment before you make the app available to users.

## Launch on your domain

Launch the app after its checks pass. You can connect a domain that you own.

## Learn and repeat

Watch where people succeed, stop, or ask for help. Use that evidence to choose the next small change.

Open the relevant surface. Make the change. Test the change. Deploy the app again.

Read the [Orbit product overview](https://orbitapps.io/) for current information about what Orbit builds and how to start. Read [Orbit pricing](https://orbitapps.io/pricing) for current pricing information.

Next, [tour Orbit Studio](/get-started/tour-orbit-studio) or [build your first app](/get-started/build-your-first-app).