Always good to receive such reviews on your content. Even so, I am currently re-recording my #JetpackCompose course to keep it up to date

Whenever I'm tempted to write such code, I pause and reflect: Who will ultimately be tasked with maintaining this? I wrote it so I understand it, but for everyone else it's obscure & challenging to comprehend Do your team a favor and write simple code, not this convoluted mess

Creating those "Empty UseCases" won't make your code "cleaner", you just end up adding multiple layers of middlemen that do absolutely nothing. No, it doesn't "help with testing" either. Your goal should be to make fake data sources, then test your real logic that uses the data.

Catalin Ghita Chris Banes As per this talk on how to TDD correctly, the best unit tests are those that use as little fakes as possible, and especially as little mocks as possible. Polluting the production code with empty stubs "just so it is easier to mock them" is the opposite. youtube.com/watch?v=EZ05e7…

Jetpack Compose team is happy to announce the release of lazy lists item appearance and disappearance animations support added in 1.7.0-alpha06 . It was the most requested feature in our bug tracker.

Catalin Ghita Chris Banes 100% this. Tell me you are not testing behaviour but implementation details without telling me you are not testing behaviour. I think this is hard to see for devs who have never done TDD the way it was supposed to be done. It was for me like that at the beginning too

It appears that someone in /r/androiddev has been working on articles about ~ Process Death ~ and how to handle Android application lifecycle problems ("it's not an edge case not an exception, it's the rule") Never forget about process death #androiddev reddit.com/r/androiddev/s…

The Jetpack Compose compiler is moving to the Kotlin by JetBrains repository with the upcoming release of Kotlin 2.0! There will be a matching Compose compiler with each Kotlin release, so you won't have to wait to upgrade the Kotlin version in your Compose app → goo.gle/3QnPCC8

🚀 Launching PiBi App Studio 🚀 A new mobile app development studio with 3 main goals: 📱 Consumer Apps 🛠 Bootstrap other apps 🤝 Experts Hub I will continue building my own consumer apps but using the learnings to create bootstrapping tools (i.e. starter-kit) to accelerate

Meet Catalin Ghita: Our Senior Android Engineer and Packt Author with 9+ years of experience, specialized in crafting and optimizing high-performance Android apps for millions of users. Learn more: pibi.studio/experts/expert…

Bought the book from Catalin Ghita to get some new perspectives about the Jetpack libraries.

Celebrating my first month of pibi studio with a giveaway! 🎉 Get a free mentoring session valued at €80! Simply follow, reply to this tweet, and stay tuned for the winner announcement tomorrow! #WhyPibi #buildinpublic

It's a nice approach but it has its trade offs. Asserting State values in your unit tests will no longer out of the box. You will either have to assert individual fields or ignore the lambdas explicitly during recursive comparison. I would not recommend the latter.

I'm launching ShipFlutter on Product Hunt today! I promise the starter kit is much better than my origami attempts at recreating the logo 🤪 Your support is greatly appreciated: producthunt.com/posts/shipflut…

Pretty thankful for the extensive documentation and samples provided by the Android team, as well as Catalin Ghita's Kickstart MAD book. This could've been clear a lot earlier if I gave them some focus early on in my Android dev journey, but hey, late is better than never!