User Profile

Hi there,I'm also working on an app for which the user experience depends heavily on Always On location authorization. I agree with most of the points that have been exposed here. Even though the intentions are genuinely good, this could kill a lot of use cases right from the first run experience.It looks like iOS 13 Beta 3 finally implements the changes advertised by Apple, and I must say the user experience regarding the new authorization flow makes absolutely no sense.During my testing I've noticed that:1. the app now receives "Always" when the user selects "When in use" when prompted in the app (what's called "Provisional always location")2. the app does not receive "Always" if the user selects "Once" when prompted3. the system only prompts the user to go to "proper always" when the phone is unlocked (no notification, that is)4. the only way the user can give the app Always permissions without being prompted first is via the phone's Settings>Privacy>Location>Your App (could not even see it in Settings>Your App any more) – and we have no way to deep-link to this Settings screen from within an app AFAIK.In my opinion these changes are very detrimental to the user experience in many use cases, especially regarding first run experience.If your app depends on background location for anything useful to the user, it's basically useless until the system decides to present the "permission upgrade" modal. It works only if the user keeps the phone unlocked and active when the location events begin, which is exactly the opposite of what users expect for background location features.