Or maybe manufacturers should stop making their own skins and customizations on Android? Because say to yourself: What a lot of misery. On the one hand, you have problems as mentioned in Don’t kill my app Where it is remarkable that Android from Samsung works differently from Android, for example, Sony. As an end user, this will hold you back anyway, since an app developer can never promise that an app will work 100% on your device flawlessly, unless they can test that specific device themselves. Source: I’m an app developer myself, and quite often I come across apps that work differently depending on the device.
However, this is also evident from Pixel problem about Tweakers I mentioned yesterday. Why does it only affect Google Pixels and not other Android devices? Why can having an app disable a default phone app? Why should a manufacturer adjust stock apps and rearrange settings menus?
It always raises questions for me, which are confirmed when I start working with the Android SDK. Many possibilities, but little thought. This gives you a lot of edge cases to be developed against, making the testing path difficult and a higher chance of bugs. At Apple, you see just the opposite, fewer options, but the SDK is better thought out and consistent. Example: As an app developer you want to verify fingerprints. On iOS, you always get a popup from the operating system. With Android, until 2018/2019 (?), you had to create a dialog yourself and build the complete pass/error case yourself and associate it with the fingerprint sensor. Why, Q, why is there no consistent dialog from the OS? And why should the plant be able to perfectly adapt it and arrange it differently? Very strange.
My position seems clear to me. Android that is modified as little as possible is in the interest of both the manufacturer and the user.
“Professional web ninja. Certified gamer. Avid zombie geek. Hipster-friendly baconaholic.”