Anyway, even including those cases it is still very far from J2ME days.
- 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.
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
?
- It does not matter if the blame is on Google or OEMs, it is still fragmented
One needs to support the home team after all.
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.
> - 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.