Thank you, you've kept me from trying to delete and reconfigure everything!
It's been months of this happening to me, on Mac too. I thought it was only me as it does not happen to my colleagues, plus it was not being fixed for so long

Great write up, as always.

If this is implemented, I see it as one big step towards the web killing mobile development.
I already saw it as a possible future, but with big barriers like this it becomes quite likely, I think.

With a lot of people saying it is super productive, I keep trying it, trying to understand if I'm doing something wrong or it is like you described.
I think this recent research may explain why many find it so productive bsky.app/profile/metr...

How does being partially covered or visible but not "resumed" (e.g. a pop-up) affect this API?

Extremely annoyed by something similar in Google maps: it auto-translates all reviews... Which costs money to Google, and is much worse UX if you happen to speak the original language.

Middle-man abstractions.
Like adding use cases with no logic, just to follow the same pattern everywhere.

It makes sense, they may feel like they lose control and also job security.
At the same time, it makes A LOT of sense from the technical and business perspectives, IMO.
I don't see a reason for doing pure native apps anymore, actually.

Hola! 👋

1, to enforce their rules, which often benefit them
2, to make it look like they provide high quality to the end user
3, to justify charging money to devs and users

🔥 Compose Multiplatform for iOS is Stable and Production-Ready! 🔥

Build mobile apps faster with shared UI code, full control over native experiences, and the confidence to ship at scale.

Explore all the updates in Compose Multiplatform 1.8.0: 👇
blog.jetbrains.com/kotlin/2025/...

I've seen a few argue in favor of TDD (not an arch, but related)

Yes, it's quite different to jetpack nav, for example. I guess I've been burned so many times by jetpack nav issues that I was OK with trying something very different. But it does take some time figuring out how it works.

I looked into the different options a couple months ago and decompose was the more complete in terms of supporting ios features (such as back gesture, animation, tab bar, etc).
I like it's state model, but it is a bit harder to get started than other options.

Pues te sugiero este libro si no lo conoces. El foco es en programación funcional, pero es con kotlin, con arquitectura Hexagonal y una forma de testear bastante interesante pragprog.com/titles/uboop...

Or tagging components for screen readers is quick, but trying it all as a user to make sure you didn't miss anything and the order and grouping are good... That's slower

Thanks for the answer! This makes sense, but what about those cases where it does take significant time? E.g. Suporting larger fonts is worthit at the start, but doing it for extreme cases (very large font, small screen) where you need a specific layout for these cases seems less straightforward.

What about accessibility? It seems to be a task you should wait on, thinking in terms of agile. But there are ethical reasons for supporting it early (and in some cases legal reasons too).

aaaHm 🤔

Jim Sproch

I remember this TIL moment too.
I couldn't understand why was I getting those crashes if I had tested config changes, until the big "oh" came.