3 ms·
OK, as you're an Android developer, I understand where you're coming from. However, Android users in 2015 pay hundreds of dollars for phones that can barely man
by rchaud 11y ago
OK, as you're an Android developer, I understand where you're coming from. However, Android users in 2015 pay hundreds of dollars for phones that can barely manage 4-5 hours of on-screen time. That is due to many factors, but users have a right to question if background app activity is to blame. Usually there isn't much quantitative information to work with, but in this case, we do have some. And it's sparked an informative discussion on HN, so I think people have benefited overall.
As for their opinion of the Priv, it's an opinion, and there have been varying opinions about it in the tech press. The way your comment was phrased, it sounded like your disagreement with their Priv review was a factor in your evaluation of their Whatsapp article.
- simoncion 11y ago> Usually there isn't much quantitative information to work with, but in this case, we do have some. As mentioned by jc4p, that tiny bit of information has provided the author with just enough rope with which to hang himself. Technical people know first-hand that the wrong information can easily lead you away from the source of a problem. Some (many?) slightly-technical people don't understand that screen-on time and cpu-awake time [0] are the major contributors to battery drain. If you provide a raw number for $ACTIONS_TAKEN [1] without establishing whether that number is in the normal range for that app and without tying that number to actual battery drain by correlating it to actual CPU or backlight usage, you're very likely to waste people's time on a wild goose chase. When making reports for non- or slightly-technical people, you usually have to be careful to filter out irrelevant information. [0] IIRC, both of which are stats that have been provided in Android for at least the past several major versions, and probably back to -at least- Gingerbread. [1] In this case, number of times contacts have been accessed by a particular app.