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.
