@marekfort gave a talk about how to scale @SwiftLang Development at Swift Rockies, which captures all our learnings from working with small and large organizations, and it is finally live: youtube.com/watch?v=f3nEV_Ux…

we are iterating ont he @tuistdev ios and android apps layout so we can land more features so you can monitor your automation activity on the go

Say hi 👋 to the new Tuist. Today we are rebranding Tuist. We started as a small command line tool that made Xcode projects easier to reason about, and somewhere along the way we turned into build infrastructure, so the brand stopped matching what the company had actually become. This rebrand is us putting a flag in the ground for where we're headed. With more code now being written in parallel and across environments, it became clear that optimizing build and test runs would stop being a problem only large enterprises had to deal with. To prepare for that future, we took a two-dimensional approach to the problem, one that lets us keep providing the experience we've always strived to give our users. First, we needed to go all the way down to the bare metal and own and deploy our own hardware, and that's what we're doing: taking that responsibility away from organizations, and provisioning environments for agentic sessions, CI builds, and remotely executed build and test run graphs. M5 Pros are coming. Second, we grew beyond the @Apple ecosystem. The new Tuist reaches across Xcode, @gradle and @bazelbuild, because the problem we are solving, which is that builds and test runs are too slow and infrastructure is too hard to run yourself, is not an iOS problem, it is an engineering problem that every team with a large enough codebase eventually runs into no matter what language or platform they build for. We want fast builds and fast tests to be something every team gets to have. Put those two dimensions together and what you get is closer to a virtual platform team than a developer tool, the kind of caching, execution and insight a real platform team would spend a year building internally, except it already exists and plugs into whatever you are running today. AI moves fast, and the teams shipping the most code with agents right now are the ones whose infrastructure can actually keep pace with how fast an agent can write, compile and test, instead of quietly becoming the bottleneck nobody notices until it is too late. We want remote caching and execution available to anyone, from anywhere, for any build toolchain out there. tuist.dev