I just published a new article, 'Compose Stability Analyzer: Real-Time Stability Insights for Jetpack Compose'. You’ll explore how this plugin works, which brings visual stability indicators to your IDE, and how the Gradle compiler plugin works. skydoves.medium.com/compose-stab...

Deferring state reads in Compose helps avoid extra recompositions ⚡️ Read state only where it’s needed, for example by passing a lambda instead of the value. Even better, use lambda-based modifiers like offset {} or drawBehind {} so reads happen in layout or draw, skipping composition completely.

I wrote a deep dive into Jetpack Compose class stability inference in the Jetpack Compose Internals book. People loved it, got great feedback. Now, @github_skydoves decided to write a masterpiece to expand on this topic. Absolute cinema, give it a read and a star! ⭐️ github.com/skydoves/com...

Go work on Compose at Google. Now!

Would you like to work on Compose at Google (Mountain View CA office)? Apply here and let's work together www.google.com/about/career...

Added a couple new features to ScreenshotWhale 🐋

Composition, Layout, Drawing. Compose goes through the 3 phases to produce a frame. But they can skip independently. Where you read state matters. Not the same reading it during composition than during layout. Thats why it’s often better to use lambda version of some modifiers.

Compose rendering isn’t magic. It runs Composition 👉 Layout 👉 Drawing (What, Where, How). No change? That phase is skipped. Change? It cascades forward only. This pipeline keeps your UI reactive without wasting work.

Studying the ones who succeeded is literal survivor bias. The real lesson is taught by the thousands who fail. Repeatable formulas for success are always BS. People improvise, grow a sense of opportunity, learn to be prepared and to execute. And the ones who fail don’t share their stories.

The main reason why my Jetpack Compose course was cohort based and now self paced is the amount of content. Too much for a live course. That’s also an opportunity to dive much deeper into all the topics. And it gives much more breathing room for attendees to take their time and make questions.

Isn't it beautiful 🤩

What is the most underrated thing you learned when working with Compose? I read you

Discussing Subcomposition and when NOT to use it 🧐 vm.tiktok.com/ZNdgAHnd4/

When you said “the number of DEVS”, but you don’t want to edit

Adding extra screenshots to any device type is possible now 🙌 I've been putting so much time and energy on creating fancy features this week that totally forgot about this super basic one 🫣🤯 Start creating your own Android or iOS app store screenshots in screenshotwhale.com 🐋

Just added project settings option to screenshotwhale.com 🐋 Now you can kick-off your screenshots blazing fast 🔥

New branding for my app screenshot generation site 🐋💦🤩 Founding members already getting access. Getting closer to the official open release every day!

My screenshot sass is changing its name because reasons. Reason #1, the name was already taken 😆 Luckily mine is going to be a much better product. Will announce the name in the following days 🐳

Your GitHub history can look like this, and it’s ok. If you know you can do a job, apply. I've met so many great devs that weren't active on GitHub publicly. We need to understand that not everybody prioritizes side projects, for many reasons. And that does not invalidate them for the job, at

The important bit is how data/state is handled (with Views its your responsibility to keep the data held in the app and in the widgets in sync).

For me, Android dev has two timelines: 🕰️ Pre-Kotlin/Compose 🚀 Post-Kotlin/Compose What would your two phases be?

Biggest shift from Views to Compose: The framework decides what to re-render, not you. Simple, but hard to achieve, and the real game changer.

My thoughts when iOS devs started complaining about having to support more than 2 form factors.

I still remember being completely lost as a junior. What helped me the most was the people who took a moment to guide me. Try to be that person for someone else.

What apps or services do you use for creating mobile app store screenshots? And what is the best feature they have that made you pick them in the first place? I hear you.

Generated these using Storeshots just now ✨ I am using the actual StoreShots own editor to quickly create all the templates that will be available in the platform.

Many of you asked, now it’s live. Just unlocked PPP pricing 🌍 and 2-installment payments for the Jetpack Compose Internals course 🚀 Don’t miss this chance to grab it cheaper before you regret it. https://effectiveandroid.gumroad.com/l/dfedea

Vibe coded apps are so unmaintainable that you can only maintain them using AI. Maybe AI knows very well what it’s doing 🥲

Do yourself and your team a favor. Don’t discard a candidate only because they don’t know about a specific pattern or a library, even if it’s very important for your team’s daily work. Many of them could simply learn it quickly. Prioritise other things.

I wrote about my journey with Compose. From sharing online, to writing a book, to launching a course, to making side income from it. If you’re thinking about doing something similar, I hope this gives you a push 🙌 composeinternals.com/how-i-made-s...

15,000 people decided to hit follow. that number feels surreal. Thank you for reading, supporting, and sharing along the way. Every connection here has made this journey richer, and i’m grateful to be part of this community. Love ya ❤️

Smart recomposition is what makes Jetpack Compose feel fast and efficient. But the real magic behind it is recomposition scopes ✨ I wrote a breakdown that explains what they are, how they work under the hood, and why they matter for performance (with examples) 👇 https://composeinternals.com/c

Love this pearl that I received some time ago for the GDE program. Looks perfect on the shelf 🤩 Compose all the things! 🦸‍♂️🚀

This codelab is really good! I'm going to comment on a few things, but other than those, this is a way better than what I've seen before! #AndroidDev

Every wondered what concurrency strategy the Compose runtime uses to coordinate state writes, and why? Learn about MVCC (Multiversion Concurrency Control) on this post I wrote some time ago. https://composeinternals.com/concurrency-control-in-jetpack-compose

This feels unreal. Every time there’s football on TV in Spain, tons of legit online businesses go down. Why? Because La Liga (Spain’s pro football league, one of the biggest in the world) forces Cloudflare to block traffic during matches to stop pirated streams. Problem is… Cloudflare also pow

People still think degrees, honors, and certificates matter in tech. Reality: no company cares. They want proof you can ship, learn fast, and solve problems.

Practical performance problem solving in Jetpack Compose 👩‍🏫 Learn how to pinpoint performance issues with system traces and composition tracing. And how to write performant Compose apps that render smoothly👇 developer.android.com/codelabs/jet...

I often think about what makes a screenshot generation service actually useful. These 4 things come up: ♻️ Easy iteration without design skills ⚡️ Produce professional results extremely quickly 📱 Support for all device form factors ✨ High quality exports at real device resolution 🎇 Neat-loo

Recent Compose versions shipped two major performance wins: - 1.5: clickable moved to Modifier.Node. Up to 80% faster composition in lists. - 1.9: LazyList APIs stable + smarter prefetch windows . Jank-free scrolls. Compose isn’t just “catching up,” it’s leaping 🚀

Modern Java is not the boring dinosaur people think. Records, pattern matching, sealed types, switch expressions, and way more. It is powerful and even more than Kotlin in some features.

Every LazyList item in Compose runs in its own subcomposition with its own slot table. When scrolled out, that slot table is cached and reused later, but only if keys match.

Walking away from programming now because of LLMs is like a photographer throwing in the towel the day digital cameras showed up. It’s a tool!

The biggest shift for me with Compose came when I stopped treating it like a black box. Once I knew what was happening inside, performance problems and recomposition issues felt less scary and more solvable.

Programmers. Twin part is that same dev can be one or the other, depending on the day. Via @midudev

Kotlin Multiplatform Wizard 🔥 https://kmp.jetbrains.com/?android=true&ios=true&iosui=compose&includeTests=true

Brutally honest Pixel 10 review via @OhThatFlo: "Last year's devices, but slightly better" The hardware upgrades are solid - better battery, Pixel Snap, improved zoom - but AI features feel half-baked. Skip it unless your phone is falling apart #android buff.ly/6JtVeo6

Facts

I've been laid off! (Startup downsizing to a skeleton crew, sadly.) I'm looking for my next dev role. Lots of experience in Android, most recently worked on Node/TS and Python. Ideally landing at a mission-driven place (been focusing on sustainability recently, but any public benefit will do).

Looking forward to that release 🤩