Previews

Tuist Previews let teammates try mobile apps, desktop apps, and command-line tools without rebuilding them locally. Publish a build to your Tuist project, then share its preview link.

What you can preview#

• Mobile apps: Android APKs and Apple application bundles or IPAs. Supported devices, simulators, and signing requirements depend on the publication workflow.
• Desktop apps: macOS application bundles.
• Command-line tools: macOS or Linux executables, on their own or bundled with their dependencies.

See Supported types for packaging and compatibility requirements. The artifact type determines where a preview can run; it does not dictate which build system produces it.

Publish a preview#

Choose your build system for setup and publication commands:

If you already have a supported build, use tuist share to publish it without a build-system integration. Packaging and signing requirements still apply.

Run a preview#

Recipients do not need the build system that produced the preview. Choose how to access a compatible build:

Visibility#

Previews use the project's default visibility. Private previews require authentication and project access. Make previews public in project settings only when the build can be shared with anyone. Public visibility does not bypass platform signing or device installation requirements.

Tracks#

Tracks organize previews into named groups, such as beta for internal testers or nightly for automated builds. Specify a track with the publication command for your workflow; tracks are created lazily when first used. Use them to group previews by purpose and filter previews in the Tuist dashboard.

README badge#

Add a badge to your repository's README that points to the latest preview:

Replace the account and project handles with your own:

If the project contains multiple apps with different bundle identifiers, add a bundle-id query parameter to choose the app: