Google is cracking down on battery-draining apps, and developers should take note! The tech giant is taking a stand against apps that impact your device's performance and user experience. But here's where it gets controversial: Google's method of 'shaming' developers might be a bold move, but will it be effective?
Google has introduced a new feature called 'wake lock technical quality treatments' to tackle the issue of apps draining batteries excessively. This feature will identify apps that keep devices awake for longer than necessary, impacting battery life. Since March 1, Google has been implementing this treatment, and it's about to get serious. Apps that repeatedly exceed the 'Excessive Partial Wake Lock' threshold will face consequences in the Play Store.
Here's the catch: if an app exhibits high background activity, a prominent red warning will appear on its store listing, stating, 'This app may use more battery than expected.' This could be a major turn-off for potential users browsing the store. However, those who are specifically directed to download the app might still go ahead and install it.
The criteria for an app to be flagged are quite specific. It must hold a non-exempted partial wake lock for at least two hours with the screen off in over 5% of user sessions in the last 28 days. Exempted wake locks are those with clear user benefits, such as audio playback or location services, which cannot be further optimized.
Developers, take note! Google's blog post offers tips to optimize your apps and avoid the dreaded warning. It covers topics like foreground services, third-party libraries, Bluetooth, and location tracking. While this is a positive step for Android users, it adds another layer of complexity for developers who already face numerous guidelines.
And this is the part most people miss: this move might make Android more attractive to iPhone users considering a switch. iOS apps are renowned for their efficient battery usage, and Google's new measures could bring Android closer to that standard.
What do you think? Is Google's approach fair to developers, or is it a necessary step to improve the user experience? Share your thoughts in the comments below!
