According to 9to5Google, Samsung and Google worked together to address inconsistencies in “foreground services and background work” between devices running the Android 14 system, resulting in OneUI 6.0.
Some OEMs have gone as far as disabling background apps to improve battery life. As a result, programs were left running in the background for extended periods of time, and end users blamed the developers for a poor user experience.
Each OEM will customize the frequency at which background apps are killed, and application developers will not be able to customize and optimize for different devices.
As a result, Google expects to address this issue with the Android 14 operating system. Google’s goal is to “make it easier for developers to create apps that work consistently across different Android devices.”
Google’s statement is as follows:
Looking to solve these consistency challenges, we are announcing deeper partnerships with Android hardware manufacturers to help ensure APIs for background work are supported predictably and consistently across the ecosystem.
Samsung has become the program’s “first partner.” Applications running on OneUI 6.0 can ensure that foreground services work as intended if they are built in accordance with Android’s new foreground service API guidelines.
Google has made three changes in Android 14:
- Application developers must declare the type of foreground service and the required permission of the defined type, which defines when it is appropriate to use a foreground service.
- Introduces data transfer task types that can be controlled by the user by exploiting JobScheduler limitations (such as network limitations, e.g. unmetered WiFi).
- The new Google Play policy ensures that foreground services and user-initiated data transfers are used appropriately.
