Whatever the services you are using, there are two mandatory delegates that your app must implement, since they’re used by all the services.
- Data Synchronisation Delegate (
NAOSyncDelegate):
Gives you the result of the data synchronisation requested by the service handle.
The synchronisation ensures the configuration data of the selected service matches the one on NAO Cloud. - Sensor Activation Delegate (
NAOSensorsDelegate):
Used to notify the user that some sensors are required by the running service, and thus should be manually activated.
Several optional services are available, each service has its Handle class and its Delegate Protocol:
- Location Service (
NAOLocationHandle , NAOLocationHandleDelegate):
Provides the location of the user in a WGS84 format. It enables you to display the user position on a map. - Geographical Geofencing Service (
NAOGeofencingHandle , NAOGeofencingHandleDelegate):
Provides geographical events when the user is entering a given zone.
This service is mainly use to engage the user with notifications or for a geographical contextualization of the digital content of your application. - Beacon Proximity Service (
NAOBeaconHandle , NAOBeaconHandleDelegate):
Provides information about the beacons around the user, this is useful to contextualize notifications or the digital content of your application when the accuracy of this contextualization is not critical. - Analytics Service (
NAOAnalyticsHandle , NAOAnalyticsHandleDelegate):
This service provides some statistics on the number of user that enter a zone.
These analytics can be seen on the NAO Analytics Plaform, but can also be exported to your back-office for custom data analysis. - Beacon Reporting Status Service (
NAOBeaconReportingHandle , NAOBeaconReportingManagerDelegate):
This service enables monitoring of your beacon infrastructure automatically; it collects information about beacons seen by your application.
This information is visible in the Beacon section of NAO Cloud.