3 ms·

>- Background tasks That's bad

by fasj82 8y ago

saagarjha 8y ago
Well, it could be good or bad, depending on how you look at it. It's foolish to argue that background tasks can't be useful. Can they also be privacy-violating battery drainers as well? Sure. I'm sure there's a right tradeoff here, and it doesn't have to be "no background tasks, period". My personal take is that it's much closer to "no background tasks" than "free reign", but your needs may vary.
- dogweather 8y ago
  Yep, an app I want to always be in bg is https://www.thetileapp.com/ https://www.thetileapp.com/
  - RandallBrown 8y ago
    Does Tile have any features on Android that is doesn't on iOS?
georgebarnett 8y ago
Background tasks become essential as soon as you need your phone to be a data aggregator for external devices. As an example, if you monitor biomedical sensors on your body, the app needs a way to reliably run in the background without being shot down.
- fasj82 8y ago
  The sensors should store the information inside themselves and then sync with the mobile when I open the app. No need to have my mobile awake all the time for something like that.
  - spacemanmatt 8y ago
    'should' Someone should redesign them, someone should rewrite OS support for them, and someone should pay for all that?
    - fasj82 8y ago
      No, they should've designed it correctly in the first place.
  - georgebarnett 8y ago
    Most sensors do tend to store data for backfill upon reconnect the designers are not idiots and have spent a much longer time thinking about this. Off the top of my head, I can immediately think of several reasons you need to pull the data off regularly: - Data is needed for real time alerting features for the user (e.g. low blood glucose). - Data needs to be uploaded to cloud services in real time so carers have access to that data so they can also be alerted. Both of these requirements require timely access to data. A delay can mean the difference between no real impact and "this user is now in hospital". I find it interesting how you can't expand your horizon to see that these features are useful to somebody that's not you.

>- Background tasks That's bad

by fasj82 8y ago

>- Background tasks That's bad

Well, it could be good or bad, depending on how you look at it. It's foolish to argue that background tasks can't be useful. Can they also be privacy-violating battery drainers as well? Sure. I'm sure there's a right tradeoff here, and it doesn't have to be "no background tasks, period". My personal take is that it's much closer to "no background tasks" than "free reign", but your needs may vary.

dogweather 8y ago
Yep, an app I want to always be in bg is https://www.thetileapp.com/ https://www.thetileapp.com/
- RandallBrown 8y ago
  Does Tile have any features on Android that is doesn't on iOS?

georgebarnett 8y ago

Background tasks become essential as soon as you need your phone to be a data aggregator for external devices. As an example, if you monitor biomedical sensors on your body, the app needs a way to reliably run in the background without being shot down.

fasj82 8y ago
The sensors should store the information inside themselves and then sync with the mobile when I open the app. No need to have my mobile awake all the time for something like that.
- spacemanmatt 8y ago
  'should' Someone should redesign them, someone should rewrite OS support for them, and someone should pay for all that?
  - fasj82 8y ago
    No, they should've designed it correctly in the first place.
- georgebarnett 8y ago
  Most sensors do tend to store data for backfill upon reconnect the designers are not idiots and have spent a much longer time thinking about this. Off the top of my head, I can immediately think of several reasons you need to pull the data off regularly: - Data is needed for real time alerting features for the user (e.g. low blood glucose). - Data needs to be uploaded to cloud services in real time so carers have access to that data so they can also be alerted. Both of these requirements require timely access to data. A delay can mean the difference between no real impact and "this user is now in hospital". I find it interesting how you can't expand your horizon to see that these features are useful to somebody that's not you.