To prioritize the work and make the right decisions, it's important to back our decisions with data. For that reason, we collect anonymous data and present it on this website for us and for the users of the tool.
Please note that this website is currently work-in-progress so the data presented is fake at the moment.
Every feature we design starts from the devise of a workflow that maps to an user's intent. For example, a user might want to focus on a target of a project, or just run the tests of a framework. Those workflows translate to commands on Tuist, for example "tuist focus". The metrics below reflect the usage of each of the workflows - understanding their usage helps us prioritize our efforts:
Where do users use Tuist? If we understand where Tuist runs, we know what we are optimizing for and what we can deprecate. For example, if Tuist is barely used with Xcode 11.3.1, it might be a good time to deprecate its support.