#Tag
Organizations tend to throw vast amounts of money at improving dev productivity with larger teams or more and faster CI machines, or moving to React Native and Bazel, but there’s a cheaper alternative that integrates natively with Xcode, and we wrote a story about it:
https://tuist.dev/blog/2025/11/17/smart-before-fast
#xcode #swift
Organizations tend to throw vast amounts of money at improving dev productivity with larger teams or more and faster CI machines, or moving to React Native and Bazel, but there’s a cheaper alternative that integrates natively with Xcode, and we wrote a story about it:
https://tuist.dev/blog/2025/11/17/smart-before-fast
#xcode #swift
Build system caching: the mechanics are similar across platforms.
Cache observability: that's where specialization matters. Working with Xcode means reverse-engineering Apple's undocumented formats to surface meaningful insights about cache performance.
At @tuist we're building Xcode-native caching with first-class observability, so iOS/macOS teams can optimize their builds with data, not guesswork.
The new tab behaviour in #Xcode 26 (for when I click a file in the navigator) will need some getting used to. Not sure why *that* needed changing
But I just figured out that in the context menu of a symbol, a click on "Jump to Definition" opens it in the same tab 😕 but a ⌥-click opens a new tab 😗
Build system caching: the mechanics are similar across platforms.
Cache observability: that's where specialization matters. Working with Xcode means reverse-engineering Apple's undocumented formats to surface meaningful insights about cache performance.
At @tuist we're building Xcode-native caching with first-class observability, so iOS/macOS teams can optimize their builds with data, not guesswork.
🎯 Back Market shares why they migrated to Tuist
Pain points: Xcode sluggish, SwiftPM froze IDE, productivity suffered.
POC results:
• 35-40% faster builds (90% with cache!)
• No Xcode freezing
• Better incremental builds
• Dynamic frameworks for dev, static for releases
The right tool fits your team's capabilities.
🎯 Back Market shares why they migrated to Tuist
Pain points: Xcode sluggish, SwiftPM froze IDE, productivity suffered.
POC results:
• 35-40% faster builds (90% with cache!)
• No Xcode freezing
• Better incremental builds
• Dynamic frameworks for dev, static for releases
The right tool fits your team's capabilities.
As codebases grow, organizing modules becomes complex. Xcode's projects force you to choose ONE organizational dimension. What if you need multiple?
Metadata tags let you organize by layer, feature, team, and platform simultaneously. Then generate focused workspaces on demand.
Combine with module caching and you only recompile what matters.
I started doing some exploration of XCBBuildService’s API. Xcode uses internally as an interface to the build system, and it’s something Bazel uses to swap the build system.
The motivation is to give @tuist access to the rawest build system data for our insights features. .xcactivitylog files and .xcresult bundles are designed for Xcode’s UI, not for analytics, and some data is either absent or not in a format that’s easy to work with.
#Xcode #Swift
me: I just upgrade to macOS26 and Xcode26, what can go wrong
Xcode: hold my beer. I won't build your project now because yadayada
I WANT TO SCREAM. Apparently #Xcode 26.0.1 has problems building Metal on macOS 26, too!
https://stackoverflow.com/questions/79660070/xcode-26-metal-compiler-error-metaltoolchain
that is a problem since Xcode 26 beta 2, and released. I'm so pissed. sooo pissed. Reported it back in Sep 9 FB20178568
I've got Xcode's build data output in a .sqlite database which LLMs can query to understand what happened in the build. The future of not wasting tokens using "xcodebuild"'s raw output is bright #Xcode
What if we could reduce the costs of end-to-end tests? It turns out it's possible with LLMs. Our Tuist QA can test your iOS apps in simulators and provide a detailed report to help debug any issues.
https://videos.tuist.dev/w/7g4HTjWxL2EgNcjXny27eZ
#Swift #iOSDev #Xcode
Xcode teams often optimize blindly:collecting build data is just too complex
With Tuist? One scheme post-action. That's it.
Here's how I added build insights to the Mastodon app in minutes:
https://videos.tuist.dev/w/mWM5SfMEwMSuRyKZu1rPmG
#Swift #Mastodon #Xcode
Another rejection for my app.
Reason: “Your app includes content or features from LG TVs, or is marketed to control external hardware from LG TVs, without the necessary authorization”
I included a chat with LG explaining I had express permission to control their TVs via their API.
I’m honestly at a loss with what to do now. I guess I don’t release it and it’s just an app for me. Incredibly frustrated and disheartened.
Another rejection for my app.
Reason: “Your app includes content or features from LG TVs, or is marketed to control external hardware from LG TVs, without the necessary authorization”
I included a chat with LG explaining I had express permission to control their TVs via their API.
I’m honestly at a loss with what to do now. I guess I don’t release it and it’s just an app for me. Incredibly frustrated and disheartened.
A space for Bonfire maintainers and contributors to communicate
