Concepts

Project

A project represents one app. Projects are created inline from the CLI's upload prompt.

Environment

A label such as dev, staging, or prod. Plain text, no schema. The CLI remembers recent values per project.

Branch

Inside an environment, branches group preview builds. Examples: feature/payments, fix/login-crash. Optional.

Checkpoint vs branch upload

The load-bearing distinction.

Branched upload

buildtree upload ./app.apk --env dev --branch feature/payments

The build is reachable at /install/folder/<project>/dev/feature/payments. The environment's checkpoint is unaffected.

Branchless upload (checkpoint)

buildtree upload ./app.apk --env dev

A branchless upload becomes the environment's checkpoint. The most recent branchless iOS and Android together form the "Latest dev" pair, served at /install/folder/<project>/dev. This is the URL to share with QA for general testing.

Build

An artifact (.ipa, .apk, .aab) belonging to one project, environment, and optional branch. The dashboard groups builds by environment, then by branch, and filters across version, build number, display name, filename, and release tag.

Install URLs

Three URL shapes (full reference on the Install URLs page):

• Pinned (/install/<buildId>). One exact build, forever.
• Folder (/install/folder/<project>/<env>[/<branch>]). Always the latest for that slot.
• Release tag (/install/release/<project>/<tag>). Frozen to a named tag.