In such scenarios Android devs were always slower on iterations compared to iOS counterparts. A few reasons of which I have highlighted above.
Things may be different in US I think, where I assume roles are more structured and scoped out.

Simply gave my view from what I have experienced :)
In all orgs I have worked in product involvement from engineering was always welcomed no matter which platform but you have to be fast in iterations.
Our product development is always more on experimentations rather market study.

Just saying in these scenarios: I wouldn't probably have written apps that want to handle screen rotation, or cared about dynamic modules, bothered to look into libraries like Haze, cared for UX on a 3 year older OS version or even any DI framework 😬

Maybe out of ignorance here: but often ios devs need not do good engineering designs.
Most ios apps I see are portrait locked (?) even today, app sizes are huge, apple forces them to use system UI components, OS updates goes to 90% user base and system has lesser resource constraints.

I have found the podcast to be more informative than all the other regular videos the big company does nowadays.

But I guess business priorities are very difficult to predict for any org.

Thanks for sharing. Went under my radar until I came across this.

💯

Compose has made it easier imo. In our app handling the view system ones have been challenging and difficult to migrate.

Cool idea for an Android launcher haha

Also the remote MCP server support is very cool e.g. accessing a Figma design and converting it into Compose code

developer.android.com/studio/previ...

Yeah. This part is so weird and unnecessary.

It's sad when OEMs don't take the best of Android.

I am curious to know how AI is actually being used inside development at Google.

I think code reviews are where AI can work somehow?!
Linting tools etc can be powerful with AI I think. But can't think of AI being used at the core workflow.

Can't unsee it now 🙈