Despite our effort to contemplate all possible project scenarios in Tuist, it’s possible that we disregarded some. As a result, you might find yourself having to workaround or fight Tuist. If you are in that situation, I’d strongly recommend bringing it up so that we can brainstorm how to handle the scenario gracefully from Tuist. We design Tuist’s APIs and workflows optimizing for the developer’s experience, and having to workaround the tool, it’s obviously not a good one.
That design principle is what makes Tuist different; it’s that principle what blows your mind, when you run
tuist generate and get all the dependencies configured in the generated Xcode project, or when you can edit your projects in Xcode and get all the documentation and auto-completion for free.
As developers, we might feel tempted to jump straight into problems without having fully understood the need/problem. That makes us go straight into using
Fastlane for dealing with certificates without even thinking if that fits our needs well. As a consequence, we end up accommodating the way we work to the way tools think we should work.
What if it was the other way around? What if the tool accommodated to the way you work?
So if you are a user of Tuist, open issues on GitHub or threads in this community forum. Let’s chat about yuour projects, about your team, about your workflows. Let’s think about how Tuist could help you with those. As a contributor or maintainer, resist the temptation of thinking in terms of solutions. Empathize with the users’ needs and problems, and brainstorm with them what’d be the best solution. Don’t constrain the solutions you come up with to what exists out there. If we think we need to something new, let’s build it! It takes time, but it pays of in the shape of an amazing developers’ experience, and that’s what make people love Tuist.