Another one that wasn't blessed with OEM deviations from AOSP.

We have "been blessed" with OEM deviations from AOSP (we have a big number of clients and most of them are using Android because of regional characteristics), but still we have way more issues with customers using out-dated iOS versions than users on those devices. For comparison, we have way more iOS issues than Android ones, even if Android is the vast majority of our user base (~70% of our customers).

Anyway, even including those cases it is still very far from J2ME days.

- Bluetooth issues

- Camera is hit and miss, even after the renewed API

- Apps randomly killed on the background

- Intents that don't launch as expected

- NDK debugging that cannot attach to the server running on the device

- Unstable GPGPU drivers

- Keyboard handling

- Perfectly working code that needs to be rewritten just because

Yeah so much better than J2ME.

You know, even if you're right we still see much more issues in iOS. For example, a simple Xcode minor upgrade can randomly break some flows.

> - Perfectly working code that needs to be rewritten just because

This issue is much more frequently on iOS than Android, since iOS deprecates features much faster and there is no compatibility layer between versions.

Except on Android that happens on the same Android version across devices.

> - Bluetooth issues

Aren't they rewriting this thing in Rust?

> - Camera is hit and miss, even after the renewed API

Give it time. CameraX is already vastly better than what we had before.

> - Apps randomly killed on the background

Up to OEMs.

> - Intents that don't launch as expected

?

> - NDK debugging that cannot attach to the server running on the device

Welp.

> - Keyboard handling

Fixed.

> - Perfectly working code that needs to be rewritten just because

?

- Devices never see updates, other than a select few flagship models

- It does not matter if the blame is on Google or OEMs, it is still fragmented

Circular arguments are circular.

Nope, just the Google support team arguments that ignore how similar Android is to J2ME in many aspects.

One needs to support the home team after all.

So now I am promoted to "Google support team" just because I bought to the discussion some observations from my own company? But you bringing your own observations does not put you on "Apple support team"? This seems completely fair /s.

Well, my point in the end is that even with all the issues that you pointed (some are true, some we didn't hit because we don't use those features), we still see more issues on iOS even when they're a smaller portion of our user base.

Heck, even if we got the most problematic Android phones for us (Asus budget phones comes to my mind), it is still has less issues than iOS.