undefined | Better HN

0 pointsklondike_8y ago0 comments

That might be good for power users, but for the average user it's a disaster. How many people actually read the app permissions when they install something? Most apps request background privileges and if you don't like that your only other option (until recently) was to not install the app.

Users blame Android when Facebook and other popular apps started eating all their battery by running in the background. Google's only choice was to aggressively punish these apps.

All developers think their app is the most important thing running on the user's system, and that is how we get into situations like this.

0 comments

2 comments · 2 top-level

dcow8y ago

Yeah I understand why we're in this situation. I'm lamenting the fact that it's reached this point. Maybe I'm a minority but I don't think my apps are the hottest shit around and I try to make an effort to be a good steward. IMO engineers should push back when product asks for things that clobber system resources. However the few bad examples should not ruin it for the use cases where you really do need something running in the background. I also partly blame these DI solutions that encourage devs to stuff everything in a graph they do or don't realize is tied to their application instance. I've seen this multiple times in production apps.

1 more reply

int_19h8y ago

So make it an opt-in mode, just like sideloading apps.

j / k navigate · click thread line to collapse