​

•  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.