It's very interesting because 1/4 of Pixel 6a would be around 80 EUR... so I wonder about your environment and what workarounds you have for these problems.

In the B2B world, we often had weird requests e.g. to take over the whole phone experience and do something different – this was made possible by the same core Android SDKs that they ship both to business devices and personal devices.

For example, we were required to move each 911 call to our app first, then check if we can route it quicker through the internal PBXs, and if not – send it back to the native/built-in dialer. This was possible a couple of years ago, we built it. I assume it's still possible because it's really rare that you need this kind of functionality... releasing such an app also requires a special review from Google. Maybe Google sees it as a low risk to the user experience and allows some apps to still do it, at least until something like this issue happes.

I'm also not surprised to read that Teams was to blame, because Skype had the same functionality back in the days.

Nexus 4, Pixel 2 XL, Pixel 4 XL, Pixel 6 Pro – never had any issues whatsoever, all phones still alive and kicking at my grandparents' places. Yes, most of them tied to the wall now... but hey, they're fine for showing some photos and displaying current time or setting alarms.

Interestingly, I also used Samsung's Note 9 and 10+, iPhone 12, iPhone 14 Pro Max – daily, also with no issues... other than disliking Samsung's software.

(I was/am doing a lot of mobile work so I test a lot of phones)

After years of doing this kind of testing, it's hard for me to believe that the entire batches of phones are so fundamentally broken... I'd rather bet on software issues, but who knows.

But overall, nowadays it's at least possible to limit the impact – compared to Lollipop era for example, when everything suddenly started to look modern, unified and nice, but still full of the same old holes.

I mean, of course, Java has been here since forever and we've made careers out of programming for JVM. I'm wondering if you are referring to a specific maturity issue, or just want to highlight that Java was here for longer... if it's the latter, I don't think it can be a valid argument against Kotlin or in favor of Java.

As far as I know, most (if not all) of the concerns shared have been addressed in the following 2 years, so I would assume that this is not an issue anymore in 2023 - or at least not as severe. I believe that new loopholes exist, but this one seems outdated to me.

However, everyone I know has a common understanding about this, so I'm not sure who would be reluctant to admit that it is the same language... outside of the very few extremist groups of course :)

Microsoft would then need to pay for ChatGPT computation, model retraining, maybe testing of deployments/upgrades, maybe sponsor Apple's initial development efforts, plus pay for the expensive deal to be Apple's default choice.

Am I understanding the problem correctly? It looks like a lot of work and very expensive if I'm getting it right.