Screw any app that really thinks it needs my precise coordinates in the foreground, let alone the background. Turn-by-turn directions in maps is the only exception I've found in 10 years of iPhone use.
Off the top of my head, any app involving directions – public transport, say – can reasonably use precise coordinates. Uber is also a reasonable use-case (when you want it to use that data) given the density of some city streets. Then there are location-sharing apps generally, or apps where you want to check in to locations (maybe a bit fuzzier, but there could be a lot of taggable locations within say 500m), or camera applications, or geocaching, or…
It's great to have control, and it would be even better if we were able to specify the accuracy an app is able to achieve. But there are obviously some reasonable use-cases for both foreground and background tracking.
For an app like that, I'd like to see a "approve every request" option. I don't always need my transit app requesting my position (even if only when in the foreground) when I really only need to look up the nearest stop occasionally.
I want to be tracked by Google. I went out of my way to turn it on in iPhone. My location is leaked to cell towers and by what wifi network I'm connecting through anyway, and I'd rather be able to figure out which cool restaurant I went to months after my visit to Vilnius is over.
Plus my memory of my personal life is so unreliable, especially if I don't have any context, so if I'm ever in court I'd like to be able to share exactly where I was when I was there.
I've stopped thinking that real privacy is attainable. That being said, I refuse to share it with scummy companies like Uber.
A car dealership who botched a warranty repair on my vehicle is stonewalling me - once they realized the error was likely to cost them $2k - $3k, their service department deleted my file and began claiming no evidence exists that I had ever been to their location. I got the scheduling department to confirm my appointment and just found my location history for that day showing that I was at the dealership right on time during the appointment. Going to send this to the manufacturer's corporate complaints departments. Thanks for the heads up.
Google's location history is excellent and I'd gladly pay for an equivalent application which I could self-host and set up with the minimum of hassle, but having them do it creeps me out too much. I've not managed to work out how to get OwnTracks to substitute fully for it.
Awesome, thanks for the link. I had been using Moves by ProtoGeo
https://appsto.re/us/PNDwE.i and it's not very accurate. Still good for going back and remembering that awesome random place you found on vacation after the fact so you can recommend it.
I also wish the NSA had something like a personal data explore, but I know that will never happen.
Unfortunately I've not found WHIB to be enormously accurate either, but it does well enough. The main nuisance is interpreting having paused whilst walking past an establishment has having gone in it.
Even Google's version couldn't get this right, at least in my case.
Explicitly decided to keep Google Maps' location history activated on my device for precisely the same reasons. I'm yet to use it in court or something like that, but the argument about human memory resonates with me strongly - I've used location history many times to review e.g. on which day I was in some place or other few years ago. (Or once, years ago, to check how exactly did I get home after one party.)
RE people saying "just take a photo and use EXIF", that won't work because I don't know in advance what locations I will be interested in in the future.
Apple's API don't discriminate with regards to precision. An app that shows nearby stores with a 1km radius precision requires the same level of permissions as an app that's trying to do 1m precision.
Apple's API allow very fine-grained control of both the accuracy and frequency of location updates, depending on, among other things, running in the foreground/background, the user's location etc.: https://developer.apple.com/library/content/documentation/Pe...
There's currently no explicit penalty for requesting too much information, but the battery power indication could probably get users to uninstall apps wasting energy, and it can even get you app terminated.
Unlike Android which have precise and coarse location. If Google wanted, they could limit precise to GPS and similar apps and force everyone else to use coarse location or geo fencing.
Unfortunately Google doesn't care about your privacy. In fact, it's only a matter of time before they remove coarse locations and/or give every app full access to location data (the same way they did with internet access).
That's a good point. Maybe app developers should be able to request the level of access they want, like precise location, neighborhood (postal code), city, state or country.
If an app never needs more precise information than the country (say Spotify trying to decide whether they operate in your country), they don't need to request it. That also guards against bugs or security breaches in apps that try to do the right thing.
Right. An application can ask for what it wants (low accuracy is much faster and burns less battery since it doesn't start GPS) but there's no way for the user to say that an app can ONLY get low accuracy data.
That's your personal choice and desired level of privacy. I like that my Lyft app knows where to set pick up and that my transit app knows the nearest street car location.
Agree with the OP that Uber can burn in hell for "always on"; I guess just in case I need an emergency Uber ride :-/
But feel free to just uninstall all those other apps that I love using.
Geotagging in photos it pretty useful. And find my iPhone. Then there's Pokemon Go - maybe not your cup of tea, but a lot of people love it. It's pretty useful to be able to share your location with someone in iMessage, I've done that a few times. Your mileage may vary.
It's great to have control, and it would be even better if we were able to specify the accuracy an app is able to achieve. But there are obviously some reasonable use-cases for both foreground and background tracking.