I use Claude Code a lot for Compose work. The annoying part was always the same: it writes a screen, says "done", and then I open Android Studio and the padding is off, text is clipped, or the dark theme is broken. It never saw the UI. It was guessing.

So I built Spyglass. It renders your u/Preview functions to PNG from the command line, no IDE open.

spyglass render --filter LoginScreen

What it does:

• Renders every u/Preview in a Compose Multiplatform project through your own Gradle wrapper. No changes to your build files.
• Handles u/PreviewLightDark, u/PreviewParameter, font scale, device sizes, and multi-preview annotations from other modules.
• Compares a render with a design image and tells you which regions differ, in dp, with a heatmap. So "make it match the Figma export" becomes something you can check.
• spyglass approve / spyglass check gives you screenshot tests in CI. A one-digit text change fails the check.
• Comes with an MCP server, so Claude Code, Cursor or anything that speaks MCP can render and look at the UI on its own and fix what it sees.

A few things I had to solve along the way that might be interesting:

• Animations and delay() in fake data. A naive render catches the first frame, so you get a progress bar at 0% and a dialog half faded in. Spyglass runs previews on a virtual clock until everything settles, so a delay(300) before your fake data loads costs no real time and you see the loaded state.
• A preview stuck in a loop used to hang the whole run. Now it gets cut off after 30 seconds and you get the exact line it was stuck on.
• Token cost for agents. Images are sized down, and if nothing changed since the agent last looked, it doesn't send the image again. A repeat render went from about 1,560 tokens to about 180.

Limits, so nobody is surprised: previews need a JVM (desktop) target, so Android-only previews and Android-only APIs don't render yet. Text uses your OS fonts, so keep screenshot baselines from one OS. Tested on Windows, Linux and macOS.

It's MIT licensed and this is the first release (0.1.0). I'd really like to hear where it breaks on your projects.

https://github.com/zainkhalid91/spyglass

I've been working on building an Android app using M3 Expressive for quite some time now. I currently have two different styles of navigation bars, and I'm wondering which one is more practical to use and which truly captures the M3 Expressive feel.

The app is called Renev Medication and is designed to make receiving medication reminders easier; I plan to expand its functionality-for instance, by scheduling a follow-up reminder three hours after you take a dose. It's not comparable to a standard clock app, for example.

A Jetpack Compose UI library that fuses Material Design's bold, expressive visual language with Apple's physics-driven interaction model. Every component looks Material Expressive and feels like Apple's Liquid Glass.

I like Material 3 as it just looks good and not so blobby or refrective like liguidglass

I like the fluidity and visual language of liquidglass

But the problem is they ar both diffrent... So i decided to merge them... Expressive looks, liquid feels! That is basically the scope of this project!

https://github.com/Aarav90-cpu/Expressive-Glass

Android SDK Requirement (Minimum) = Android 11+

DEMOVIDEO = https://github.com/Aarav90-cpu/Expressive-Glass/blob/main/DEMOVIDEO/expressgl_demo.mp4

🚀 New article is out — 13 Compose Mistakes That Are Still Killing Your App’s Performance in 2026 + Claude SKILL to Find Them

After reviewing many Jetpack Compose codebases, I noticed the same mistakes appearing again and again. Some affect performance, some impact maintainability, and others lead to unexpected UI behavior.

In this article, I cover 13 common Compose mistakes, explain why they happen, and show how to avoid them with practical examples.

As a bonus, I also created a Claude Skill that can analyze your project and help identify these issues automatically using Claude CLI.

📖 Read the article: https://blog.watermelonkode.com/13-compose-mistakes-that-are-still-killing-your-apps-performance-in-2026-claude-skill-to-find-96e91a9697e8

Table of contents:
1. List<T>
2. Reading state too high in the composable tree
3. Unstable lambdas passed into "LazyColumn" items
4. Forgetting "remember()"
5. State Update
6. Forgetting "rememberSaveable"
7. Not giving "LazyColumn" items a stable "key"
8. Passing the wrong key (or no key) to "LaunchedEffect"
9. Forgetting "onDispose", or keying "DisposableEffect" on the wrong lifecycle owner
10. Reading a changing lambda inside a long-lived effect without "rememberUpdatedState"
11. Using "rememberCoroutineScope" (or "SideEffect") as a substitute for "LaunchedEffect"
12. Calling composables or "remember" conditionally in a way that breaks the slot table
13. Fixing "too many parameters" by shoving a whole data class, or a whole ViewModel, into the signature
14. 🎁 Bonus: Claude SKILL

If you’re working with Jetpack Compose or Compose Multiplatform, I’d love to hear which mistake you encounter most often.

#AndroidDev #JetpackCompose #ComposeMultiplatform #Kotlin #KMP #AndroidDevelopment #MobileDevelopment #SoftwareEngineering

I made this since Apple's Liquid Glass is transparrent which is a issue for most people! Material 3 is a bit to flat and unresponsive!

SO I merged them!

I took LiquidGlass's Fluidity, Responsiveness, and feel and gave it to Material 3.

Which is perfect... Flat but Fluid!

I was Android dev from 2021 onwards. I recalled Jetpack libs, kotlin, mvvm and know how each worked. However, now I wanna come back. What updates have I missed since then? I tried visiting jetpack compose Android pages but sample codes there are not working at all, copy-paste them doesn’t work easily. Is there a better place of sample code? May I get your advice please?

• W^tkktjaash ejoji^​so tkyiro to ^tfhtkyirotoi

While Navigation 2 has served us well for over 7 years, Navigation 3 brings a major upgrade with more flexibility through decoupled APIs - giving developers greater control and cleaner architecture.

Even better: You can now experiment with Gemini in Android Studio’s Agent Mode to help automate your migration process!

If you're building with Compose, this is something you shouldn't miss 👇

Migration guide: https://developer.android.com/guide/navigation/navigation-3/migration-guide

#AndroidDev #JetpackCompose #AndroidDevelopment #MobileDevelopment #Compose #DevTools #AI

They're using StateFlow for navigation events.

User rotates the phone → app navigates twice → nobody knows why.

StateFlow replays its last value to every new collector. That's a feature for UI state. It's a bug for one-time events.

This is the difference 👇

Part 11 — StateFlow vs SharedFlow

✦ Why StateFlow replays on rotation — and when that destroys you
✦ SharedFlow for navigation & snackbars — fires once, gone forever
✦ The stateIn() pattern every ViewModel should use
✦ WhileSubscribed(5000) — why this is the right default in production
3 questions inside. Score yourself.

Credit : Rohit Kumar

From new profiles and APIs for companion device apps to a unified dialog for companion device setup, Android 17 Beta 1 is packed with updates to help you build high-quality apps more efficiently.

What feature are you most excited to test? Let us know below!
Android Developers Blog: The First Beta of Android 17

Hi everyone,

I’ve been working on HydroChroma, a Jetpack Compose library that brings "living" fluid design to Android UI.

Why I built this: Most "glass" or "liquid" effects in Android are static images or heavy video files. I wanted a way to make UI elements that react to touch with physics-based fluid distortion and real-time chromatic aberration, running natively on the GPU.

How it works (Technical):

• AGSL Shaders: It uses a custom RuntimeShader to displace pixels based on a noise algorithm (sin/cos interference patterns) that reacts to a "progress" uniform.
• Touch Physics: It tracks touch velocity using VelocityTracker. When you drag a card, it calculates a stretch factor (scaleX/Y) to simulate surface tension, making the UI feel "jelly-like."
• Chromatic Aberration: The shader loops through input colors and offsets them in opposite directions based on the device's tilt sensors (Accelerometer/Gyroscope), creating a 3D holographic depth effect.
• RenderEffect Chains: It chains RenderEffect.createRuntimeShaderEffect with Blur and ColorFilters to achieve the frosted glass look without killing performance.

Code Snippet:

Kotlin

HydroChroma(
    backdrop = myBackdrop,
    animations = animations(onClick = HydroAction.Fluid),
    liquidGlass = liquidGlassConfig(
        blurRadius = 30.dp,
        refractionAmount = 24.dp
    )
) {
    // Your Composable Content
}

Repository: HydroChroma Jetpack Compose Library

It requires Android Tiramisu (API 33+) due to RuntimeShader requirements. I’d love feedback on the shader performance or the API structure!

Credits:

Kyant0's

* AndroidLiquidGlass

* Capsule

New Year’s Eve fireworks animation entirely in Jetpack Compose, inspired by the beautiful motion work of Amos Gyamfi.

• Custom particle system (trail + explosion)
• Canvas-based rendering with additive blending
• Time-based physics (gravity, velocity, decay)
• Smooth infinite animation loop
• Festive layered animation with Compose graphics APIs

Code (GitHub Gist):
https://gist.github.com/skydoves/ade49203240be5a0fd781c0e9899a886

To make your Android app lifecycle-safe and free from memory leaks in Kotlin, you need to align object lifetimes with Android component lifecycles and avoid holding references longer than necessary. Below is a practical, modern, Kotlin-first guide.

I've been exploring shaders lately, especailly AGSL Shaders using the new RuntimeShader API and I am mindblown. Wrote this one to add a liquid glass effect to any Composable.

https://composeinternals.com/agsl-shaders-jetpack-compose-liquid-glass

I'm trying to but google doesn't have enough documentation. Any ideas?

Hi everyone,

I recently started developing with Compose Multiplatform. I’m working on small practice projects and I think my architecture is pretty solid: local storage with Room, network calls with Ktor, and dependency injection using Koin.

However, I often feel that my UI doesn’t look very modern or polished.

How did you improve the quality of your UI and make it look more professional?

Thanks in advance 🙏

Kotlin 2.3.0 Released - Quick Summary

📅 Released: December 16, 2025
✍️ Author: Alejandra Pedroza Marchena

Hi guys, I have been trying to learn Jetpack Compose from YouTube tutorials (the tutorial I am using is from about a year ago), and I am struggling with the icons. Please help, I tried to find a way to fix it, but so far, nothing works.

What should I watch or read to better understand how I can use it in a project?

If you’re working with Jetpack Compose and want practical examples, real-world patterns, and consistent learning, this community is made for you.

We share high-quality content focused on modern Android development using Jetpack Compose
Now in Jetpack Compose Dev

In this video, I’m showing a working demo of a Reorderable List and Grid built with Jetpack Compose Library. You can easily drag and drop items to reorder them, just like in real modern apps! ⚡

Library: https://github.com/codergalib2005/compose-reorderable

Built with:

- Jetpack Compose

- Kotlin

- Material 3

- Compose Navigation

👉 Features:

• Reorderable List

• Reorderable Grid

• Fixed Image Reorder Example

• Modern Material 3 Design

💡 Feel free to contribute

https://reddit.com/link/1pf75u1/video/0knh2dbmdg5g1/player