←
JetpackCompose.app518 posts
JetpackCompose.app avatar

JetpackCompose.app

@JetpkComposeApp

The #1 destination for all things Jetpack Compose. Keeping up with Android Development is hard. We make it easy, entertaining and rewarding. Made by @VinayGaba

◷ Joined July 2022▧ 213 Photos and videos
JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4 Jul 2022

Folks, we have finally landed on Twitter 🚀 Give us a follow for the latest and greatest about Jetpack Compose - the best way to build Android apps. Help us spread the word if you want to avoid 5 years of bad luck 😂 jetpackcompose.app/ #AndroidDev #JetpackCompose

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4h

Docs developer.android.com/develo… This was in Dispatch #24. Stuff that saves you a day of crash archaeology is the kind of thing I write about there jetpackcompose.app/newslette…

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4h

The catch is release builds need Kotlin 2.3+ with R8 on, and group key traces only point at the first line of each composable. Still a lot better than guessing which screen blew up. What's the worst Compose stack trace you've had to decode?

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4h

Compose then rebuilds your composable hierarchy and attaches it to the crash as a suppressed exception. Auto uses group keys in minified builds, nothing otherwise. For local debugging there's SourceInformation. Exact lines, but it costs about as much as Layout Inspector.

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4h

If your Compose crash reports are all ComposerImpl and SubcomposeLayout frames with none of your code in them, add this to Application.onCreate(): Composer.setDiagnosticStackTraceMode(ComposeStackTraceMode.Auto) Do it before any composition gets created.

Post attachment
JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·4h

A rule that only lives in your AGENTS.md will get broken eventually. Long agent sessions are where it slips. The rules agents keep breaking should be tests. On Android, Konsist lets you write "the domain layer depends on nothing" as a plain unit test.

Post attachment
JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

Tbh those failures are useful. Your app never ran coroutines instantly, so some of those green tests were hiding real races. One more: if you use createComposeRule together with runTest, you get two separate test clocks. runComposeUiTest gives you one.

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

So this test passes on the old rule and fails on v2: viewModel.loadData() assertEquals(Success, viewModel.state.value) When the assert runs, loadData() is still sitting in the queue. Call composeTestRule.waitForIdle() first, or move the assert into runOnIdle { }.

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

Moving your Compose UI tests to the new v2 test rule can turn a green test red, even though your app didn't change. The old createComposeRule() ran a launched coroutine right away. The v2 one puts it in a queue, and it only runs when the test lets it.

Post attachment
JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

Then keep the file short enough that you'd actually read it. Steps for a migration you run twice a year belong in a skill, which only loads when the task matches. Put them in AGENTS.md and every rename-a-composable session pays for them.

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

Without the first one, a terminal agent doesn't know the android binary exists, so it goes hunting for gradlew and guessing sdkmanager flags. Run android init to install the android-cli skill. The official Claude Code and Codex plugins do the same thing.

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 16

The most useful lines in an Android repo's AGENTS.md are the boring ones. I'd start with these two: Use the android CLI for SDK, emulator, deploy, previews and docs. Don't grep the SDK. Run the module's test task before you say you're done.

Post attachment
JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 13

The 47% is real. What I want to write about is what I'd practice next as an Android engineer, and how I'd use agents on actual app work. That's Dispatch: Context. It's free. jetpackcompose.app/newslette…

JetpackCompose.app avatar
JetpackCompose.app@JetpkComposeApp·Nov 13

US software postings on Indeed are up ~15% since Feb 2025. 71% of that growth was senior roles, 37% had AI in the title. The Android title is shrinking faster than the work. I'd aim at owning features past the app, with agents doing much of the typing. hiringlab.indeed.com/2026/07…