Connect with us


Twitter’s Jetpack Compose Rules – Static checks of Compose

It can be challenging for big teams to start adopting Compose, particularly because not everyone will start at same time or with the same patterns. Twitter tried to ease the pain by creating a set of Compose static checks.

Compose has lots of superpowers but also has a bunch of footguns to be aware of as seen in this Twitter Thread.

This is where our static checks come in. We want to detect as many potential issues as we can, as quickly as we can. In this case we want an error to show prior to engineers having to review code. Similar to other static check libraries we hope this leads to a “don’t shoot the messengers” philosphy which will foster healthy Compose adoption.

Check out the project website for more information:

Static checks for Compose bundled in this repo

You can find the comprehensive list of rules in the rules documentaton. It contains both the what and why for each rule, we encourage you to read it prior to adopting our rules.

There are 2 ways you can add these static checks to your build – using ktlint or using Detekt.

Jetpack Compose Rules Using with ktlint

dependencies {
    ktlintRuleset "com.twitter.compose.rules:ktlint:<VERSION>"

For more information, you can refer to the Using with ktlint documentation.

Jetpack Compose Rules Using with Detekt

dependencies {
    detektPlugins "com.twitter.compose.rules:detekt:<VERSION>"

For more information, you can refer to the Using with Detekt documentation.

Jetpack Compose Rules on GitHub:
Platform: Android
⭐️: 778