Managing application settings
Under the Applications view you have the capability to manage fine-grained details of how your mobile application functions. Click on the Edit button next to the token you want to configure.
1. Managing technologies
Under each application you have the capability to specify, what technologies you app uses. You can easily start with for example native positioning, and add BLE beacons later on. Leaving beacons off in your apps means that your app does not ask your end users a permission to use Bluetooth.
|Native positioning||Enabled (GPS-level)|
How are the technologies used:
Native positioning: You will utilize the native location data received through Google or Apple Location services. Your application will be requesting the user to enable GPS/Location, when native positioning is enabled.
With Android, you can define how battery-consuming and accurate your positioning data will be. Cellular has the least effect on the battery, and only utilizes the location deducted from the information of the nearby cellular towers, but also results in poor accuracy. Wifi utilizes both cellular and Wifi information, and has a good balance between accuracy and battery-efficiency. It is in most cases the optimal option. GPS utilizes in addition to the two previously mentioned also the direct GPS information from satellites. It is very accurate, but consumes a lot of battery. Important note: These options have no effect on iOS applications – Apple does not allow you to control the location data received with this detail.
iBeacons: Turning iBeacons on means that your application will be listening to BLE beacons transmitting with the iBeacon specification. Your app will be requesting the user to enable Bluetooth (and depending on phone model, also GPS/Location), if iBeacons are enabled.
Eddystone: Turning Eddystone on means that your application will be listening to BLE beacons transmitting with the Eddystone specification. At the moment you can only utilize UID and TLM through your application. Your app will be requesting the user to enable Bluetooth (and depending on phone model, also GPS/Location), if Eddystone beacons are enabled.
IndoorAtlas: Your application will be utilizing geomagnetic positioning through the IndoorAtlas technology. Using IndoorAtlas does not require any specific permissions in the mobile application, though WiFi and Bluetooth will improve the positioning data. Please link your IndoorAtlas account information here, and also for the respecting Place and Floor.
2. Advanced Settings
Now we are getting really to the specifics of how your application should navigate between the different technologies used in your setup. We recommend that you take a good look at the explanations below, before you change any of these.
Geofence positioning: The geofence positioning is a privacy setting. Use it to limit that the position updates will only be stored within geofence areas. This is excellent for example for workplace applications, where the employer only wants to see how the staff has been moving at their working area, and not see where they have been moving in their spare time.
Trilateration: Trilateration is on as a default. It is the calculation of your positioning based on multiple location sources or multiple beacons at a time. Turn it off, if for some reason you would want to utilize individual beacons.
Network Interval: As a astandard, our SDK communicates event to our backend in real-time. If you would want to set it to sync up less frequently, turn on network interval, and specify a network interval value in milliseconds. (Warning! Activating this setting can mess up your account, do not activate without prior discussion with Proximi.io team)
Native Activation Treshold: As a standard, when our SDK detects an indoor venue, it will disregard the native positioning information until it has not heard from any other technology for 30 seconds. Then it will switch back to native positioning. If you would like to change this setup to either direction change the native activation treshold value (in milliseconds).