--- title: Xcode and Gradle: Two worlds, one infrastructure | daily.dev description: Tuist shares lessons from extending its build tooling infrastructure to Gradle after years of working with Xcode, comparing the two build systems across... canonical: https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Xcode and Gradle: Two worlds, one infrastructure | daily.dev og:description: Tuist shares lessons from extending its build tooling infrastructure to Gradle after years of working with Xcode, comparing the two build systems across... og:url: https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii og:image: https://api.daily.dev/og/posts/hOEFDTiiI.png og:image:alt: Xcode and Gradle: Two worlds, one infrastructure og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Xcode and Gradle: Two worlds, one infrastructure **[ Tuist ](https://daily.dev/sources/tuist-blog)** · 19 min read · 0 upvotes · 0 comments ## Summary Tuist shares lessons from extending its build tooling infrastructure to Gradle after years of working with Xcode, comparing the two build systems across caching, build insights, test insights, and distribution. Gradle's rich plugin API (BuildCacheService, OperationCompletionListener, TestListener) let Tuist ship remote caching, build insights, test insights, flaky test detection, bundle analysis, and previews for Gradle in about three weeks, versus months for Xcode. Xcode's closed architecture forces workarounds: parsing binary .xcactivitylog files, proxying gRPC calls for Apple's new compilation cache via a Unix socket daemon, and using scheme post-actions since there is no plugin model. The piece concludes that Gradle's extensibility is a genuine ecosystem advantage while Xcode's constraints shape every third-party tool that integrates with it. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does Xcode 26's compilation caching work under the hood? Xcode 26 introduced compilation caching built on LLVM's Content Addressable Storage (CAS), which stores and retrieves artifacts by the hash of their content, similar to how Git stores objects. It works at sub-function level granularity, letting Xcode skip recompiling individual compilation units when their inputs haven't changed. The remote cache interface is a gRPC protocol with no public SDK, accessible only via a Unix socket that a locally running service must expose. _Track how Apple's toolchain changes affect build caching workflows by following Xcode updates on daily.dev._ ### Does Gradle support remote build caching natively? Yes, Gradle has built-in remote build caching that has been stable for years, configured simply by enabling it in gradle.properties and pointing it at a remote service. The protocol is plain HTTP: before running a task, Gradle sends a GET request with the task's cache key, and if there's a hit it downloads the artifact instead of executing the task; after execution it uploads outputs with a PUT. _Compare build caching approaches across ecosystems like Gradle and Xcode on daily.dev before picking your infrastructure._ ### Why is it harder to build developer tooling that integrates with Xcode compared to Gradle? Xcode has no plugin model, so there's no way to hook into compilation events, intercept caching, or listen for test results as they happen. Tools must instead wrap xcodebuild, parse undocumented binary formats like .xcactivitylog and .xcresult bundles after the fact, and run daemons as gRPC proxies for features like remote caching. Gradle, by contrast, exposes stable, documented interfaces like BuildCacheService and TestListener that plugins can implement directly. _Developers weighing platform tooling investment can dig deeper into build system internals via daily.dev._ ## Similar posts on daily.dev - [Toss: Building less to ship faster](https://daily.dev/posts/toss-building-less-to-ship-faster-1arhtus0n) · Tuist · 4 upvotes · 0 comments - [The new Tuist, from build toolchains to bare metal](https://daily.dev/posts/the-new-tuist-from-build-toolchains-to-bare-metal-waw3c6jvd) · Tuist · 0 upvotes · 0 comments - [Bazel remote caching and insights in Tuist](https://daily.dev/posts/bazel-remote-caching-and-insights-in-tuist-mdlrtqhx3) · Tuist · 0 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#xcode](https://daily.dev/tags/xcode), [#gradle](https://daily.dev/tags/gradle), [#build-systems](https://daily.dev/tags/build-systems) [View this post on daily.dev](https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Xcode and Gradle: Two worlds, one infrastructure","url":"https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii"},"datePublished":"2026-08-23T12:20:02.275Z","dateModified":"2026-08-23T12:43:29.125Z","description":"Tuist shares lessons from extending its build tooling infrastructure to Gradle after years of working with Xcode, comparing the two build systems across...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6e1a7a340e64d85d637a16377f5e0bd?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6e1a7a340e64d85d637a16377f5e0bd?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"\n Tuist\n ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"\n Tuist\n ","logo":"https://media.daily.dev/image/upload/s--3AYDH23h--/f_auto,q_auto/v1787487506/logos/tuist-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/tuist-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,xcode,gradle,build-systems","timeRequired":"PT19M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"\n Tuist\n ","item":"https://daily.dev/sources/tuist-blog"},{"@type":"ListItem","position":3,"name":"Xcode and Gradle: Two worlds, one infrastructure"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/xcode-and-gradle-two-worlds-one-infrastructure-hoefdtiii#faq","mainEntity":[{"@type":"Question","name":"How does Xcode 26's compilation caching work under the hood?","acceptedAnswer":{"@type":"Answer","text":"Xcode 26 introduced compilation caching built on LLVM's Content Addressable Storage (CAS), which stores and retrieves artifacts by the hash of their content, similar to how Git stores objects. It works at sub-function level granularity, letting Xcode skip recompiling individual compilation units when their inputs haven't changed. The remote cache interface is a gRPC protocol with no public SDK, accessible only via a Unix socket that a locally running service must expose. Track how Apple's toolchain changes affect build caching workflows by following Xcode updates on daily.dev."}},{"@type":"Question","name":"Does Gradle support remote build caching natively?","acceptedAnswer":{"@type":"Answer","text":"Yes, Gradle has built-in remote build caching that has been stable for years, configured simply by enabling it in gradle.properties and pointing it at a remote service. The protocol is plain HTTP: before running a task, Gradle sends a GET request with the task's cache key, and if there's a hit it downloads the artifact instead of executing the task; after execution it uploads outputs with a PUT. Compare build caching approaches across ecosystems like Gradle and Xcode on daily.dev before picking your infrastructure."}},{"@type":"Question","name":"Why is it harder to build developer tooling that integrates with Xcode compared to Gradle?","acceptedAnswer":{"@type":"Answer","text":"Xcode has no plugin model, so there's no way to hook into compilation events, intercept caching, or listen for test results as they happen. Tools must instead wrap xcodebuild, parse undocumented binary formats like .xcactivitylog and .xcresult bundles after the fact, and run daemons as gRPC proxies for features like remote caching. Gradle, by contrast, exposes stable, documented interfaces like BuildCacheService and TestListener that plugins can implement directly. Developers weighing platform tooling investment can dig deeper into build system internals via daily.dev."}}]} ```