Barely a week ago we had the arrival of Android 13 on Google Pixel and among all its details we are left with this novelty that will put a good wall for phone manufacturers. Above all, it aims to make things very difficult for them when they force close third party apps.
[13 pequeñas novedades de Android 13 que van a mejorar mucho la experiencia en tu móvil]
Cheerful Third-Party App Developers
Phone manufacturers are justify in these application closures in the background always with the aim of extending battery life, but the ones who suffer are third-party app developers who have been badly affected for years.
Disadvantaged by the fact that their apps not working completely and they end up closing without the user even realizing it. In other words, apps start, you set them up, and since many have to be open in the background, they end up wasted due to malfunctioning.
Android 13’s CDD now requires OEMs to provide a “clear, public document or website that outlines how proprietary restrictions are enforced.”
This MUST be linkable from the Android SDK docs and MUST include the following:
— Mishaal Rahman (@MishaalRahman) August 18, 2022
Via Android Police, we know that the requirements to which they are subject Manufacturers have been updated with a measure that requires them to submit documentation on how restrictions are applied to background apps.
OnePlus, Samsung and others made sure app developers suffered headache when your apps are forcibly closed. But now they will have to show what conditions apply to the restrictions, how an app can be exempted from them, or how they can require an exception.
Battery in apps
The free Android
It’s a big step towards finally on android 13 any app can be present without the pressure exerted by a brand to leave in the background only those that interest it. Well, of course, some surely find a loophole with which to continue with such restrictive measures and the experience on an Android mobile is not adequate.
You may be interested
Follow the topics that interest you
