Hi -
Summary:
I would like my app to offer a warmer message regarding the authorization prompt.
Detail:
This is a suggestion. While working with iBeacon my app requests authorization from the customer to: "Allow [app] to use your location". Ideally for my iBeacon app I would like the app to run essentially all the time, so the authorization request the app makes is: requestAlwaysAuthorization
Subsequently iOS will ask the user if they would like to continue to allow the app access to location. This is all appropriate and I'm happy with Apple's focus on privacy (! thank you)
My suggestion:
Decouple iBeacon from Location for the user. My point is that Location (CLLocation - things on a map), feels clunky when considering proximity relative to iBeacons. Namely items of such small resolution typically aren't found on a map. An example: we don't typically think of a topographical map to represent and navigate our house and iBeacons lend themselves to that kind of environment (among others). Things are either 'near' or 'in the next room' or 'in the garage' or 'in the car'. You get the idea.
Why do I want this?
I would like to the app to offer a warmer message regarding the authorization prompt "Allow [app] to use your location" - sometimes this prompt has the backdrop of an 'map'. Perhaps something like this:
"Allow [app] to access your proximity to iBeacons."
Thanks so much!
Be well.
PS: NFC won't work for my application. My design doesn't accommodate the user moving the iPhone close to the artifact. Rather the phone needs to be ranging for the artifact silently and the app operate in the background.
Summary:
I would like my app to offer a warmer message regarding the authorization prompt.
Detail:
This is a suggestion. While working with iBeacon my app requests authorization from the customer to: "Allow [app] to use your location". Ideally for my iBeacon app I would like the app to run essentially all the time, so the authorization request the app makes is: requestAlwaysAuthorization
Subsequently iOS will ask the user if they would like to continue to allow the app access to location. This is all appropriate and I'm happy with Apple's focus on privacy (! thank you)
My suggestion:
Decouple iBeacon from Location for the user. My point is that Location (CLLocation - things on a map), feels clunky when considering proximity relative to iBeacons. Namely items of such small resolution typically aren't found on a map. An example: we don't typically think of a topographical map to represent and navigate our house and iBeacons lend themselves to that kind of environment (among others). Things are either 'near' or 'in the next room' or 'in the garage' or 'in the car'. You get the idea.
Why do I want this?
I would like to the app to offer a warmer message regarding the authorization prompt "Allow [app] to use your location" - sometimes this prompt has the backdrop of an 'map'. Perhaps something like this:
"Allow [app] to access your proximity to iBeacons."
Thanks so much!
Be well.
PS: NFC won't work for my application. My design doesn't accommodate the user moving the iPhone close to the artifact. Rather the phone needs to be ranging for the artifact silently and the app operate in the background.