قالب وردپرس درنا توس
Home / Gadgets / Google admits that white is bad for battery life after all its apps have been whitened – Droid Life

Google admits that white is bad for battery life after all its apps have been whitened – Droid Life



"We've got a bit of a run in terms of performance."

Google's Android Dev Summit has been running since Wednesday morning and was the site for Google's confirmation that foldable displays will come and support Android. However, Google hosted a specific session titled "Pixel Color Cost" yesterday, which may be the most important feature of the entire event. I would say, "important" in one, Google just had to admit how much they have been showing up in their app designs lately and hopefully the change will come soon.

What was the big issue at "Cost of a pixel color", you ask? Battery life differences between dark and light app designs. Guess which one was better for battery life? I do not think you have to tell me that, but Google has admitted that the developers have probably wrongly forced the developers to exaggerate white.

The session displays a series of funny statistics and charts, all of which compared a phone with a starkly white theme with a with a dark theme and the influence of battery life. Look at this shit. If you adjust the brightness of your phone, you can save 21% on your keyboard with a damn dark theme.

Well, that's all important, because Google spent the past year making all its apps stupid, overly ridiculous. We made fun of every update, especially because pure white apps are boring, but this just shows you the degree of stupidity. And this session is probably why they start offering dark modes and themes for each updated app.

After it became known that white is bad and dark is good, the session was about how developers can easily implement dark themes, other colors in themes, dark or black colors for AMOLEDs, etc. If anything, this should be one Good news for those of us who like dark topics and hate the overuse of white in apps. I am sorry that it took until 2018 before Google realized this.

// Slashgear


Source link