Integration workflow

Integration workflow

This page gives useful information for the project management aspect of the integration of the SDK.

  •  Planning and effort estimation for the integration of the SDK:
    • Coding effort: 1 staff day per OS, integration support : 1 staff day
    • Testing effort: 1 staff day per OS
    • Publication delay: 1 day for Android, 2 weeks for iOS for the first publication, 1 week for iOS publication updates
    • SDK Integration can be done before, during or after deployment
  • Integration procedure to follow / checklist:
    • Configure Android / iOS project to include the SDK
    • Manage permissions / authorizations
    • Implement main business use cases of the application (Blue dot on map, etc)
    • Implement sensor activation requests (Bluetooth chip requested, etc)
    • Implement error handling (synchronization error, etc)
    • Implement issue reporting
    • Testing
  • Testing methods:
    • If the fingerprinting is not done, the SDK can be tested in the office using location simulation. In simulation mode, the SDKs will send out locations pre-defined in a file (.kml) downloaded from the cloud.
    • If the fingerprinting is done, the SDK can be tested in replay. In replay mode, the SDKs will read measurements recorded in a file (.gwl), and compute locations as if the device was on site.
      • Copy the gwl file (get gwl file from evaluation logs on Nao-Cloud) in the path of your application like this:[
      • [Android] :  /sdcard/Android/data/your.app.package/files/.nao/replay/
      • [iOS]:  /Apps/$yourapp/Library/Application Support/data/replay/
    • The last tests should be executed on site, for a range of devices.

    • Related Articles

    • Integration workflow and recommendations

      This page gives useful information for the project management aspect of the integration of the MQTT API. Planning and effort estimation for the integration: Coding effort: from 1 to 2 staff days, integration support : 1 staff day; Testing effort: 1 ...

    • Geofencing integration

      NAOGeofencingHandleDelegate This class provides the callbacks for receiving alerts configured on NAO Cloud in the Geonotifications section. The recommended implementation is as follows: Make the class where you want to receive the callbacks implement ...

    • Self-hosted integration

      This page describes how to configure NAO Logger and NAO SDK when using the NAO Server default installation parameters. In the .env file in the self-hosted install folders you used to deploy NAO Server, the server IP and port information are defined ...

    • Release 20.06 (NAO SDK 4.9)

      Release 20.06 NAO Cloud – July, 9th 2020 New Features Import Visioglobe places as geofences. Beacons guidelines conformity: a new heatmap is now available, highlighting the areas that do not meet the radio requirements for the location engine. It is ...

    • Emulate User Position

      If you want to test your integration of the NAO SDK without the need to be on site, we provide an emulated mode. That emulated mode is only available for the Location Service and Geofencing Service. Warning: The emulator mode bypasses the sensors, so ...