Jose Mendoza

@chandmohd0305 @JorgeCastilloPr Use graphic layers is good 👍

@jose_7com @JorgeCastilloPr Is it bad thing to use graphic layer ?

“I should wrap everything in remember / derivedStateOf / key just in case.” Very obvious premature optimization, but also very common. These tools are great when you need them, but. sprinkling them everywhere adds complexity and can even hurt. Measure first. This behavior normally comes from people with little knowledge about Compose internals. They don’t understand the system and they fallback to adding patches everywhere. Avoid doing that, take a deep breath, inspect the source code and learn.

If someone look this , do you use special skill for read the ui performance on Android apps ? Or some extra tool ?

@phonescloud99 I’m using this mix Claude + Maestro I just make an experiment , tomorrow I Try to do with real phone, and yes I test the apk , hit the api and run feature flow

@jose_7com Nice role split. Does the QA agent actually launch Android tests or an emulator pass, or is it mostly checking the generated code against the Android skills docs?

Built a multi-agent pipeline in Claude Code: architect → developer → QA → code reviewer, from a single command. Each role Google's official Android Developer skills. 🤖⚙️ #AndroidDev #Kotlin #AI github.com/android/skills

anthropic reunió a 6 ingenieros que crearon Claude en Londres. nadie habla de ello todavía. compartieron lo que va a cambiar tu forma de construir para siempre: → agentes que se coordinan entre sí → Claude que recuerda tus sesiones pasadas → criterios de éxito que defines tú → ventana de contexto tendiendo al infinito pero el dato que más me impactó lo dijo el Director de Producto: "el código que escribes para compensar las limitaciones de Claude... será inútil en 6 meses." el código que conecta Claude a tu mundo, en cambio, va a ganar valor. hay una línea muy fina entre construir sobre la IA y construir contra ella. la keynote entera está en el vídeo de abajo. esto es todo, nos vemos mañana.

@maestro__dev What happens if you use and extra Hardware device for your app ?

You don't write e2e TESTS anymore. Your agent does.

I will prepare the tools for create design system with Claude + Android studio + Pencil from Design and Pm

🫡

Your Google AI subscription now includes Gemini in Android Studio. 🤖 Google AI Pro and Ultra subscribers now have higher limits and dedicated capacity for Gemini in Android Studio → goo.gle/4dtC42E #GoogleIO

Android Studio Quail.1 is STABLE! 🚀 We're bringing efficiency gains to your debugging workflows, letting you fix complex crashes seamlessly with AI-generated code→ goo.gle/quail1 Here’s what’s new: ⬇️

Every single choice, whether choosing an in-memory or disk cache, comes with a cost 🧠💰 If you want to master the framework behind these complex architectural decisions, this book is a game-changer. Check out the TOC & free preview chapters: 🔗 manuelvivo.dev/mobilesystemde…

Jetpack Navigation 3 is stable! 🎉🎉🎉 Leaning into Jetpack Compose and the idea of combining smaller building blocks together really helped make Nav3 a much more flexible library that made it a joy to work on and hopefully for you to use as well! android-developers.googleblog.com/2025/11/jetpac…

The Android ecosystem is expanding with new form factors and users expect experiences that run reliably across devices. Watch this LIVE #GoogleIO session to learn about: 🎨 New APIs and updates to Jetpack Compose ⚒️ New tools & Skills ➕ And more goo.gle/4uryMEI

vibe code @Android apps directly in AI Studio and test on your phone get started today: ai.studio/build

Build for Android, your way. 🛠️ In the era of agentic development, we’re giving you the flexibility to build apps using any AI tool, agent, or LLM you choose. See what's new: stable Android CLI v1.0, expanded Android skills, and fresh models on Android Bench → goo.gle/4393Mx9

Complex workflows require specialized knowledge. ⚡ We’re expanding our Android skills repository to help models master specific patterns. With 17+ skills covering AppFunctions, Adaptive UI, and more, adding domain expertise is just a CLI command away → goo.gle/4vvyAo0

Check Compose Navigation Graph 🔥

Compose Skill Suite version 4.0.0 is out now I added a new feature to help with animations

"Inline callbacks in Composables are killing my performance." This is a widespread misconception. Lambdas can allocate, but the cost is often vastly overstated. Non-capturing lambdas are cheap, and capturing lambdas only become interesting when they are recreated often enough to matter. More importantly, recent versions of Compose handle this case much better than old advice suggests. Historically, an inline callback such as onClick = { viewModel .select(id) } would often create a new lambda instance during recomposition. The concern was not the allocation itself, but the fact that a new lambda instance could make parameter comparisons fail, preventing child composables from being skipped even when nothing meaningful had changed. With strong skipping enabled, the Compose compiler automatically remembers many lambdas passed to composable parameters. An inline callback like onClick = { viewModel .select(id) } can be treated as if it had been wrapped in remember{}, using the values it captures as keys. As long as those captured values remain the same, the callback keeps a stable identity across recompositions, making it much easier for Compose to skip work that doesn't need to happen. In most apps, lambda allocations are nowhere near the top bottleneck. Don't rewrite clean, readable code based on a vague fear of allocations if you haven't measured first.