Updated to Android Studio Meerkat (stable release) and I cannot simply run the app (shift + F10) after clearing the project anymore. Awesome 😄 Issue issuetracker.google.com/issues/3767072… #AndroidStudio

Android Studio Meerkat has a broken run configuration. The solution: Menu -> Run -> Edit Configurations -> "Before launch" sections -> Add the task "Gradle-aware make" Video on YouTube youtu.be/VDcKBywHUMI #androiddev

Indie Dev log NeonFrame.app I see the number of users who uses the app started growing in March, but nothing was changed for 2 m. No updates & store page changes. The rating was changed 🌟 Thanks to in-app rating pop-up & to users who don't skip it #buildinginpublic

+5🌟 Love users who takes a minute to write a few words. It motivates. Screenshot Maker - NeonFrame.app #buildinpublic #androiddev

A new Android app idea is in progress ⏳️ #buildinpublic #androiddev

Faced out with the UI performance issue using nested Lazy lists in Lazy grids inside a Horizontal Pager. UI slightly freezes till I set a delay for displaying lists inside the grid. #androiddev #buildinpublic #jetpackcompose

Fixing UI performance issues. An interesting thing I noticed after Baseline Profiles was implemented. The UI was slightly changed, and I didn't regenerate the Baseline Profiles. The number of frozen frames jumped up again from 10% to 24% #androiddev

Fixing UI performance issues I got a question where to see frozen frames metrics. Google Play console -> left menu -> Monitor and improve -> Android Vitals -> Overview -> Scroll down a bit and look for Rendering section #androiddev

In December 2024 I had been chosen to be a participant in the Device Streaming program from Samsung, Xiaomi, Oppo, OnePlus, and realme Lab in Android Studio. And now all nuances of usage are clear to me patreon.com/posts/part-3-e… #androiddev

I like the Gemini's deep research feature. Instead of googling. It finds articles, source codes on GitHub, analyzes them, and gives the conclusion. #androiddev #Gemini

Trying to add support for devices with 16 KB memory page sizes. Play Google console ⚠️warns about. Followed steps from the docs. Upgraded native code. Upgraded Gradle. Read tons of useless articles. And the warning is still there. Curious what I missed 🤔 #androiddev

The most interesting thing about the Google Play requirement to support 16 KB memory page sizes on 64-bit devices is that my app without any 3rd party native code has that warning as well. Guessing it's because of outdated gradle. No any ideas how to fix it. #androiddev

Well. The Gradle upgrade solved the issue. No more warning about 16 KB memory page sizes support. It was the app without native libs. #androiddev

It's been almost 3 years since I published on Medium. A new article is out . Based on my experience building a PDF Maker app for Android. medium.com/@mobiledevpro/… #androiddev

Thanks to Google. Spent hours to find out there are deprecated functions in an internal Material 3 library 👌🏻 Even the latest 1.4.0-alpha still has it. Warnings from Google Play console - Android Vitals #androiddev

Love Google's surprises. ML Document scanner has a RAM usage limitation. Minimal 1.7 GB. Noticed it in the Crashlytics. #androiddev

Once a year the same thing. It's a Google Play console. And it's a critical warning. I've already updated some of my and client's apps to the target API 35. The most time-consuming part is "edge-to-edge" support if you haven't implemented it before. #androiddev

Still the most difficult part to me in Jetpack Compose is debugging. In most cases Firebase Crashlytics and Android Vitals refers to deep internal components in stack traces. And it seems in August '25 Google improved the crash analysis and added a dignostic stack trace

Jank-free scrolls 👌🏻 I still cannot figure out where jank/frozen frames come from in the app with lists and thumbnails on almost every screen. My current percentage is about 20% Google Play console displays and it's +15.9% vs peers' median I would like to improve.