Hi,
I would like to enquire the frequency that iOS will check for beacon regions, and if this is variable what factors go into account when deciding how often to check. Is there a specific worst/average/best case that we can expect?
Through our testing, we have seen the cycle time range from 1 second to 5 minutes.
The significant variable of time is not an ideal user experience, if we know what contributes to the variables, we can better manage our user experience.
Cheers,
I have the same question : what variables contribute to region monitoring event frequency?
In iOS 10, I'm seeing didEnterRegion / didExitRegion callbacks anywhere between 1 second and 30 seconds after I manually start / stop the beacon. I understand that more aggressive monitoring would increase energy consumption and immediate notifcations are not practical. I'm simply looking for guidance from the CL team on the algorithm used to determine when to scan/detect beacon region events and notify the delegate.
The region monitoring frequency is impacted by a variety of factors, none of which the app can control. If you want your device detected faster, make sure it complies with the iBeacon advertisement intervals. Many low cost solutions (just about all using button batteries and claiming multi-month battery life) attempt to have longer battery life by violating the iBeacon Technology standards and advertising at intervals outside the specifications.
