- Google wants to know more about developers’ app restriction experiences on Android.
- Developers can fill in a survey naming the OEMs and providing additional details.
Smartphone makers want to give users more battery life by killing unnecessary apps in the background. However, some OEMs perhaps take this practice a little too far. Now, Google wants to hear from developers how OEM software from Android makers is affecting their apps.
Spotted by XDA, app makers can now fill in a survey detailing how OEMs’ “app restriction” practices on Android are culling their apps. “If your app is restricted due to battery saver, please provide as many details as possible in the form below,” asks the form. Google specifically wants developers to name the OEM responsible, among other details.
Background app killing has been a long-standing issue on Android. Google has taken some action to ease developers’ pains. It outlined plans before Android 11‘s launch to give developers more control. More recent Android versions have implemented better resource management systems to ensure essential apps aren’t killed while abusive apps are. However, some OEMs are still found to kill background apps, which may disadvantage smaller developers more.
Which OEMs are responsible?
Some popular Android smartphone makers are reportedly chief culprits, too. DontKillMyApp called out Samsung as the worst offender after Android 11 landed. According to the site, the likes of Nokia, OnePlus, and Xiaomi were also on the list.
This practice might be a nightmare for developers, but smartphone users still believe aggressive battery management on modern smartphones is necessary. According to an Android Authority poll, nearly two-thirds of respondents felt this way. Hopefully, the survey is the latest step for Google to find a balance between the concerns of OEMs, developers, and users.
If you are a developer and have experience with a specific or multiple OEMs culling your app in the background, you can comment by heading to the survey at the link.
