Our first cycle is over, and we’re about to kick off the second one, running from May 26th to July 6th. I’d like to share what the team is planning to work on during this new cycle.
Build Analytics
We’re bringing build analytics to the dashboard and might take this opportunity to revisit our approach for storing analytical data—potentially using ClickHouse. We’ll start by surfacing the information we already have and lay the foundation for collecting additional insights that developers find useful. We’ll also draw inspiration from what Develocity offers.
Content Addressable Store (CAS)
We’ll begin developing expertise around content-addressable stores (CAS), which could be introduced to Swift’s build system at WWDC or in the near future. We’re considering Bazel’s contract as a reference, and we’ll create a performance benchmark to evaluate the latency of various solutions. This will help us understand where our infrastructure stands today and how we can optimize it.
Cache Analytics
As more organizations adopt binary caching, a natural question arises: What’s the impact?
We’ll collect and present estimates—both in the CLI and the dashboard—on the time saved and the percentage of the dependency graph converted to binaries. This should give teams a clearer picture of how Tuist is improving their workflows.
Previews Improvements
Interest in previews has been growing, and we believe they have the potential to unlock seamless collaboration. That’s why we’re investing more in them. In particular:
- We’ll support grouping simulator and device artifacts from the same commit under a single link.
- Users will be able to download only the platform-specific previews they need.
- We’ll sign (or re-sign) the app on the fly at installation time, removing the signing burden from developers.
Marketing Website Redesign
Now that the new dashboard is out, our marketing site feels a bit out of sync. We’re working on fixing that. We’re elevating the craft of the website to align with the dashboard’s design language and match the quality of other developer tools in the ecosystem.
If there are any websites you admire, feel free to share them with us.
Alongside these initiatives, we’ll continue addressing critical issues and reviewing community contributions across all areas of the project. I’d love to hear your thoughts!