Get started
Pick the path that matches how your app is built today. Each one walks through what to install, how to enable caching, insights, and testing features, and how to verify the setup end-to-end. You can adopt them independently, or combine them if you ship on more than one platform.
Most paths use the Tuist command-line interface. Elixir uses the Hex package, and Once connects through its native Tuist provider; neither requires the Tuist CLI for its integration.
Xcode project#
Keep your existing Xcode project or workspace and add Tuist capabilities one at a time. No project generation required.
Start with an Xcode project →Generated Xcode project#
Let Tuist define and generate your Xcode project from Swift manifests. Generated projects compress the complexity of modular Xcode projects into a concise, declarative description of the graph, and are a strict requirement for the module cache and selective testing.
Start with a generated project →Gradle project#
Connect a Gradle project to Tuist's remote cache, build insights, and test insights through the dev.tuist Gradle plugin.
Elixir project#
Connect an Elixir project to Tuist's build insights, test insights, flaky test detection, and test sharding through the tuist_ex Hex package.
Rust project#
Run Cargo through the Tuist CLI to report builds and individual test results, including doctests, and investigate flaky tests.
Start with a Rust project →Bazel project#
Point a Bazel workspace at Tuist's Remote Execution API cache and Build Event Service to share cache hits and insights across your team and CI.
Start with a Bazel project →Once project#
Connect Once's cacheable scripts and build graphs to Tuist for shared caching, live build and test insights, hosted test sharding, and application previews.
Start with a Once project →