What is lawnchair built with?

lawnchair is a Java repo built with Jetpack Compose, androidx.compose.runtime:runtime-livedata, androidx.navigation:navigation-compose, com.google.dagger:hilt-android, core-ktx, and 1 more. It stores its data in androidx.datastore:datastore-preferences, reaches it with room-ktx and room-runtime, makes its content with coil-compose and androidx.exifinterface:exifinterface, and is tested with espresso-core, org.jetbrains.kotlinx:kotlinx-coroutines-test, rules, ui-test-junit4, ui-test-manifest, and 8 more. It has 866,975 written lines, with 1,391 test files.

Read on November 9, 2026, at commit ce82ac1. Read it as markdown

Frontend

The base 3

Styles 1

  • ui-text-google-fonts

Interface 17

  • com.google.android.material:material2 files
  • androidx.recyclerview:recyclerview40 files
  • androidx.core:core-animation28 files
  • androidx.constraintlayout:constraintlayout21 files
  • com.google.accompanist:accompanist-drawablepainter7 files
  • com.airbnb.android:lottie5 files
  • androidx.preference:preference-ktx4 files
  • androidx.window:window3 files
  • sh.calvin.reorderable:reorderable3 files
  • androidx.graphics:graphics-shapes2 files
  • com.google.accompanist:accompanist-adaptive2 files
  • dynamicanimation
5 more
  • foundation-layout
  • graphics-path
  • material3-window-size-class
  • ui-graphics
  • ui-util

Icons 1

  • androidx.compose.material:material-icons-extended33 files

Backend

Data 1

  • androidx.datastore:datastore-preferences12 files

Data access 2

Support

The base 3

  • com.google.dagger:dagger73 files
  • com.google.dagger:hilt-android
  • core-ktx

Content 2

Testing 13

  • Google315 files
  • org.jetbrains.kotlinx:kotlinx-coroutines-test
  • junit:junit1,185 files
  • org.mockito:mockito-core335 files
  • androidx.test.ext:junit289 files
  • org.mockito.kotlin:mockito-kotlin264 files
  • androidx.test.uiautomator:uiautomator176 files
  • androidx.test:runner29 files
  • androidx.benchmark:benchmark-macro-junit42 files
  • espresso-core
  • rules
  • ui-test-junit4
1 more
  • ui-test-manifest

Tools 10

  • com.google.errorprone:error_prone_annotations4 files
  • com.google.dagger:hilt-compiler
  • androidx.profileinstaller:profileinstaller1 file
  • dagger-android-processor
  • dagger-compiler
  • ktlint-cli
  • leakcanary-android
  • room-compiler
  • ui-tooling
  • ui-tooling-preview

Other 16

  • com.google.guava:guava
  • JetBrains
  • javax.inject:javax.inject207 files
  • androidx.lifecycle:lifecycle-viewmodel-compose9 files
  • com.google.accompanist:accompanist-permissions4 files
  • com.android.tools:desugar_jdk_libs2 files
  • androidx.concurrent:concurrent-futures1 file
  • byte-buddy
  • byte-buddy-agent
  • converter-kotlinx-serialization
  • core
  • kotlinx-serialization-json
4 more
  • leakcanary
  • okhttp
  • retrofit
  • service

Other repos with a similar stack

Ordered by how much of its stack they share with lawnchair, then by stars.

Frequently asked questions

What language is lawnchair written in?
lawnchair is written in Java, with 866,975 written lines.
What framework does lawnchair use?
lawnchair is built with Jetpack Compose, androidx.compose.runtime:runtime-livedata, androidx.navigation:navigation-compose, com.google.dagger:hilt-android, core-ktx, and com.google.dagger:dagger.
What database does lawnchair use?
lawnchair stores its data in androidx.datastore:datastore-preferences and reaches it with room-ktx and room-runtime.
Does lawnchair have tests?
Yes. lawnchair has 1,391 test files and is tested with espresso-core, org.jetbrains.kotlinx:kotlinx-coroutines-test, rules, ui-test-junit4, ui-test-manifest, junit:junit, org.mockito:mockito-core, Google, androidx.test.ext:junit, org.mockito.kotlin:mockito-kotlin, androidx.test.uiautomator:uiautomator, androidx.test:runner, and androidx.benchmark:benchmark-macro-junit4.
Which repos have a stack like lawnchair's?

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →