Hola 
!
As we close out the third development cycle (July 14 - August 24, 2025), it’s time to reflect on what the team has accomplished and share insights into the upcoming fourth cycle. This update provides a comprehensive overview of the progress made, challenges encountered, and the exciting roadmap ahead.
Cycle 3 (3rd Cycle / July 14 - August 24, 2025)
Major Achievements
Tuist QA: From Concept to Near-Reality
As you know, we began this cycle with the assumption that LLMs could play a role in minimizing the costs of acceptance tests. These tests bring significant value to teams but are used sparingly because they’re costly to develop and maintain.
We set out to validate this idea by building a solution on top of previews that would pull a preview, test it using context from your project and PRs, and return a report to increase your confidence before merging your work.
The team did an exceptional job, and the results look very promising. Like any solution that places LLMs at its core, we’ll need to iterate with your help to maximize the value you get back. However, we believe LLMs can be quite instrumental in this phase of app development.
We’ve started testing with some customers and will gradually expand the testing group until we can make the feature generally available (GA). If you’re interested, let us know in this thread and we’ll add you to the testing program. Here’s a sneak peek of what the reports might look like in our dashboard:
As part of this work we’ve invested in integrating with Namespace, a piece of work tha we’ll leverage down the line for other features that require running one-off tasks in macOS environments.
Website Transformation: More Than Just a Fresh Coat of Paint
The website redesign has made significant progress this cycle. The team has been crafting an experience that better communicates Tuist’s value proposition to both newcomers and existing users.
This isn’t merely an aesthetic update – it’s a complete rethinking of the information architecture, user journey, and visual language. The implementation is underway, with the new design system taking shape to ensure consistency across all touchpoints, from documentation to dashboard. This cohesive experience reflects Tuist’s evolution from a project generation tool to a comprehensive infrastructure for Apple app developers.
As we move forward, the website will play a crucial role as the first touchpoint for developers discovering Tuist QA and understanding how it fits into their development workflow. The messaging is being carefully crafted to clearly convey the value proposition while maintaining technical accuracy.
Binary Caching Infrastructure: Preparing for the Future
Binary caching has always been at the heart of what makes Tuist special – and it’s about to become even more critical as Apple rolls out their content-addressable storage system.
This cycle, we made a significant infrastructure move: adopting Tigris for global cache distribution. What does this mean for you? Your cache artifacts are served from the nearest location, wherever you are in the world.
We’ve started rolling this out to some users, and the early results are impressive. P90 latencies have dropped from hundreds of milliseconds to under 100ms – a dramatic improvement that makes pulling cached builds noticeably faster.
We’re taking a measured approach to the rollout, gradually expanding to larger customers as we ensure the service remains rock-solid and reliable. This careful deployment ensures everyone gets the best possible experience.
With the changes coming to Apple’s build system, having this improved caching infrastructure means you’ll be better prepared for whatever comes next. Every performance gain matters when you’re iterating on your app.
Other impactful work
- Buildable Folders Support - Added support for buildable folders, enabling new project organization capabilities and build optimizations - @pepicrft - #7984
- Bundle Management Commands - Introduced
tuist bundle listandtuist bundle showcommands for better cache bundle inspection and management -
@pepicrft - #7893 - XcodeKit SDK Support - Added support for XcodeKit SDK, enabling Xcode extension development within Tuist projects - @navtoj - #7993
- MacOS App Running Support - Extended tuist run command to support macOS applications, completing cross-platform run capabilities - @pepicrft - #7956
- ClickHouse Migration for Analytics - Migrated CommandEvents to ClickHouse for enhanced analytics performance and scalability - @cschmatzler -
#7793 - Binary Source Preservation - Added support for keeping source code of targets replaced by binaries, improving debugging capabilities - @pepicrft - #8000
- Continuous CLI Releases - Implemented automated continuous release pipeline for the CLI, ensuring faster feature delivery - @pepicrft - #7902
- RunAction Enhancement - Added filePath and customWorkingDirectory support to RunAction for more flexible execution contexts - @plu - #8071
Cycle 4 (September 1 - October 12, 2025)
The 4th cycle of the year began this week, and here’s what we plan to focus on.
Tuist QA
We’ll onboard the first users and iterate on the feature based on their feedback. We’re also implementing a dedicated report page in our dashboard that provides more detailed information than what we can display in GitHub PR comments, where we’re limited by markdown’s capabilities. We’ll surface the most relevant information directly in the PR and link to the dashboard for comprehensive reports. As mentioned earlier, if you’re interested in testing this feature, please let us know and we’ll add you to the testing program.
Website
We’ll advance both the design and implementation of the new website. We believe you’ll love it because it aligns perfectly with the new dashboard design and better captures what Tuist is evolving into through its information architecture: comprehensive infrastructure for mobile developers.
Streamlined GitHub Integration
With Tuist QA, some users won’t need to install a CLI just to create a project and connect it to their GitHub repository. We’ll make these workflows web-based and implement the already-designed UI for connecting Tuist projects with GitHub repositories.
As part of this initiative, we’ll explore OIDC authentication support, enabling the CLI to generate OIDC tokens directly from GitHub Actions environments and validate them against GitHub. This eliminates the need to manually create tokens, store them as secrets, and configure pipelines to use them.
Join Us for the Community Call!
We’d love to connect with you face-to-face! Join us for our upcoming Tuist Community Call next week where we’ll dive deeper into these updates, demo some of the exciting features in development, and answer your questions.
When: Register on Luma to see the time in your timezone
What to expect:
- Live demos of Tuist QA in action
- Sneak peeks at the new website design
- Q&A session with the team
- Discussion about future directions
- A chance to share your feedback and ideas
Whether you’re a long-time Tuist user, considering adoption, or just curious about what we’re building, we’d love to see you there. It’s a great opportunity to connect with other developers in the community and directly influence Tuist’s roadmap.
Can’t make it? No worries! We’ll share a recording afterwards, but there’s nothing quite like being part of the live conversation.
See you there! 