Announcing Tuist Build Insights
Sooner or later in the lifecycle of any software project, you’ll find yourself needing to iterate on its setup and tools to ensure your momentum doesn’t fade. We often refer to this as scaling development. It’s inevitable. The tools and practices that once worked start to break down as the project grows larger, with multiple modules, complex dependencies, a team of contributors working in parallel, and a growing test suite ensuring reliability.
Among all the factors at play, one of the most critical—because it directly affects the feedback loop—is build time. Build performance tends to degrade as projects grow, often due to unreliable incremental builds, derived data resets, or changes in the project graph or toolchain (e.g., explicit modules) that can impact parallelization. Understanding build times is essential for making optimizations and improving development velocity—but doing so is far from straightforward.
While the toolchain provides data—like the build graph—raw output alone isn’t enough. First, you need to make that data accessible. Second, data that’s isolated in time or scope may not reveal much. But if you persist it over time and correlate it with the team activity—tying it back to specific developers or workflows—then meaningful insights start to emerge.
At Tuist, we don’t want to just help teams optimize workflows through better tooling; we also want to empower them with actionable data to make smarter decisions—whether to boost productivity or improve developer happiness.
That’s why we’re thrilled to introduce Tuist Build Insights: our solution for collecting and analyzing build data from your Xcode projects, across any environment—including local development.
For the full announcement, head over to Measure, analyze, and improve your build times with Tuist Build Insights.
And as always, we’d love to get your feedback! Feel free to post any ideas or issues you might have run in this thread 