In my journey of becoming a developer responsible for the infrastructure of large scale applications, Tuist played a central role. It was the tool we chose to scale and maintain an Xcode workspace with tens of projects and frameworks, while keeping the iOS team sane.
The initial argument for adopting it was project generation, and we would never again see a merge conflict in .pbxproj files. But Tuist is much more than that!
It can help your team in the following ways (and many more!):
- have standardized Xcode projects and targets, making it easy for every developer to spin up new modules
- define your targets and projects explicitly, with Swift code, and reuse common definition
- link frameworks by other frameworks or by the main application, free of Xcode intricacies
- cache frameworks and SPM dependencies for faster builds
- understand your targets dependencies graph
In the last 2 projects I worked on, I worked on the transition to Tuist. Every second spent on it was worth it. In large teams, there is working with Xcode before and after Tuist. But even if you’re an indie developer, you can take advantage of the benefits it can bring to your day to day.
Check out tuist.io to learn more about it, get started, and make your team more efficient today.
My sincere thanks to the Tuist team for being the first sponsor of Swift Toolkit!