Democratizing making informed decisions when evolving an Xcode project

[pepicrft]

Tuist democratized tackling complex challenges by providing simple solutions with little cost for teams. We want to go further and democratize making informed decisions when evolving an Xcode project, and for that, we need your input.

Putting the technicalities aside, I'd love to ask you to think about what data you'd love to have in your team to improve the health of your Xcode project. Health is a very broad term and can mean many things. Still, in this context, we are particularly interested in knowing what would make a developer want to work on that project (e.g., deterministic and fast tests, seamless collaboration...). Or, looking from the opposing angle, what are the things that would make a developer go away from the project or the organization abstract away the platform with solutions like React Native?

Let me know in a thread here. Please be problem-oriented. For example, "I would like to know test coverage" is a solution-oriented answer. I'm interested in what you'd do with the data, different from what you'd like to collect. Once we understand your needs, we'll be able to figure out what data is needed and how to present it.

Be creative! Refrain from letting current Xcode and tooling capabilities limit your thinking. Some of your ideas might be unfeasible, but we can go far to turn them into reality, like caching via Xcode projects.