[vxNsr]

Classic HN response.

I'd guess a FTP and a linux file-server would solve all your filesharing woes as well.

No dev making a mass market device or software should build as if the 1% graybeard engineer is gonna be the only user, that's a lot more user hostile.

[admax88q]

The "which apps are using battery" feature is easily useable by novice users.

However most phone vendors incorrectly assume "background connections" will drain battery life despite evidence to the contrary.

Phone vendors have a vested interest though in forcing developers to use their proprietary "push" feature for syncing to phones, they say it's for "battery life" but really its about vendor lock in.

A well engineered app can sync over its own TCP connection just fine and not hurt battery life, but then such an app can work on any device, not just blessed Android builds that have access to GCM.

[stickfigure]

Android's "these are the apps killing your battery life" interface is perfectly usable by Joe Everyuser. This is a specious argument.

[vxNsr]

Reality suggests otherwise.

Every modern phone today will give you a list of the apps that take the most juice, and yet somehow for some reason people still install facebook. We might need to protect users from themselves.

[admax88q]

Or users could start holding facebook accountable for shitty battery life.

I don't understand why phone manufacturers need to add features to protect facebook users from facebook. facebook has the money to build an app that isn't shit.

[dithering]

Never mind HN, that's a classic Slashdot response.