--- title: "Let's defuse the Compose BOM" url: https://daily.dev/posts/let-s-defuse-the-compose-bom-b1ajyi9eb source_url: https://jakewharton.com/defuse-the-compose-bom type: article source: "Jake Wharton" published: 2026-07-05T07:13:18.003Z updated: 2026-07-05T07:13:44.350Z tags: ["android", "jetpack-compose", "gradle"] reading_time: 4 upvotes: 0 comments: 0 language: 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. # Let's defuse the Compose BOM **[Jake Wharton](https://daily.dev/sources/jakewharton)** · 4 min read · 0 upvotes · 0 comments ## Summary Jake Wharton argues that the Compose Bill of Materials (BOM) is largely unnecessary for modern Android projects. He explains that AndroidX libraries already bundle peer dependency constraints in Gradle module metadata, automatically aligning sibling artifacts within the same library group. The Compose BOM only covers five library groups with four distinct versions, which tools like Renovate or Dependabot can track individually. Additional drawbacks include inconsistent release cadence, a date-based version number that obscures real library versions, and partial override issues when adopting AndroidX betas. Wharton recommends defining Compose library group versions explicitly, the same way any other dependency is managed. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [jetc.dev Newsletter Issue \#300](https://daily.dev/posts/jetc-dev-newsletter-issue-300-owejri5uu) · Jetpack Compose Newsletter · 0 upvotes · 0 comments --- Tags: [#android](https://daily.dev/tags/android), [#jetpack-compose](https://daily.dev/tags/jetpack-compose), [#gradle](https://daily.dev/tags/gradle) [View this post on daily.dev](https://daily.dev/posts/let-s-defuse-the-compose-bom-b1ajyi9eb)