jnrelectric.blogg.se

Using iBeacons requires more battery power from your mobile device when using location services.Bluetooth signals can be vulnerable to interference.Using iBeacons requires that FileMaker Go has access to location services.

iBeacons are low energy Bluetooth devices and therefore have a limited range.

“Background” monitoring in this case just simply refers to the fact that the monitoring is automatic and doesn’t need to be triggered with a user action as it did in FileMaker Go 15. FileMaker Go 16 still must be the front-facing, active application in order for the monitors to trigger. This is not the case with FileMaker Go 16 region monitoring. For example, iOS mail operates in the “background” and can still receive email even though you are looking at a website on mobile Safari and may not even have the mail app open at all. Typically with iOS development, the term “background” means that the app in question is not the front-facing app on the device. Why is “background” in quotes you may ask? Well, this is so we don’t confuse nomenclature. With the release of FileMaker 16, FileMaker Go 16 can now monitor for region events in the “background” and we are now able to monitor for iBeacons in FileMaker Go without having to invoke a script manually with a button or other action. The trouble with that was that it had to be triggered by a user action and couldn’t be invoked automatically. FileMaker 15 gave us the “RangeBeacons” function which allowed FileMaker Go to “poll” for known beacons.