Because it adds to the software complexity. several boolean toggles for deciding what to incorporate into the localization algorithm: one toggle for GPS, another for wifi, Bluetooth, cell tower, barometer, etc. and fusing these in all the various combination, testing them, etc.
and after doing all that users will mess up their config and then complain that this app sucks not knowing someone on HN had this feature request for "privacy" reasons even though it's pretty unclear to me what privacy is being gained here.
Apple products generally don't give the user much choice and decide what's right for the UX and it's served them well
Though the software complexity was already there, and they decided to remove it (by adding another kind of software complexity), effectively deleting a feature that apparently people are using.
It cannot even be claimed to be an UX improvement since it's creating disruption for everybody that had this feature disabled.
At this point they should have added it to the terms of use and deleted the toggle directly (which I suspect they are going to do down the line, when they can prove that nobody keeps that toggle off).
gerash|4 years ago
and after doing all that users will mess up their config and then complain that this app sucks not knowing someone on HN had this feature request for "privacy" reasons even though it's pretty unclear to me what privacy is being gained here.
Apple products generally don't give the user much choice and decide what's right for the UX and it's served them well
thegrasshopper2|4 years ago
It cannot even be claimed to be an UX improvement since it's creating disruption for everybody that had this feature disabled.
At this point they should have added it to the terms of use and deleted the toggle directly (which I suspect they are going to do down the line, when they can prove that nobody keeps that toggle off).
Terretta|4 years ago