Use Cases

This is currently a work in progress and will be released soon!

General

The following are general points you need to cover:

  • The version number of your mobile application and our SDK needs to be easily visible for the end-user during runtime of your app
  • On screens with interactions with an IoT device, you need to provide an easy to find help indicator. Using this link, will open an in app webview with the following URL:

    https://mobile-in-app-support.sensorberg.com?os=$os&app_version=$app_version&sdk_version=$sdk_version&phone_model=$phone_model

    • $os: android or ios
    • $app_version: your app version e.g. 2.3.4
    • $sdk_version: the version of our SDK e.g. 1.2.3
    • $phone_model: the model of the phone e.g. iPhone 11 or Google Pixel 2

    Based on this information, we can provide the end user faster support.

Tests

Online Tests

Please log into your mobile app, ensure that the phone is connected to the internet with Bluetooth activated and run the following tests:

Ensure activated Bluetooth

Your app shows a warning, that interactions with IoT devices are not working, when the user deactivates Bluetooth anytime during usage.

List of accessable locks

Your app should show a list of locks the user has access to.

List of accessable locks, which are nearby

Your app should show a list of locks the user can open now.

Opening a lock successful

Your app should be able to open a lock succesfully

Failed opening should show an error message

A failed interaction with the lock should show one of the available Error codes

Ensure opening animation reflects the feedback from the SDK

The animation for opening a door, switching on a light, etc. should reflect the real feedback provided by the SDK. If the action is not successful, the user should NOT see a succcessful animation but rather negative feedback.

Ensure user session stability

User should be able to kill the app and relaunch it without the need to login again

Ensure app scans for devices, coming from background

Ensure, that the app stil scans for nearby devices, even when coming back from the background after several minutes or hours.

Logout

Logout of the mobile app with current user. Log into the mobile app with a second user, open a door and prove with the backend log entry, that the second user was opening the door.

Offline Tests

Please log into your mobile app, put the phone into Airplance mode, with activated Bluetooth and run the following tests:

Ensure activated Bluetooth

Your app shows a warning, that interactions with IoT devices are not working, when the user deactivates Bluetooth anytime during usage.

List of accessable locks

Your app should show a list of locks the user has access to.

List of accessable locks, which are nearby

Your app should show a list of locks the user can open now.

Opening a lock successful

Your app should be able to open a lock succesfully

Failed opening should show an error message

A failed interaction with the lock should show one of the available Error codes

Ensure user session stability

User shoud be able to kill the app and relaunch it without the need to login again

Ensure app scans for devices, coming from background

Ensure, that the app stil scans for nearby devices, even when coming back from the background after several minutes or hours.

Things to consider

Auto deactivation of mobile SDK after specified timeframe

Please note that our SDK will require re-initialization following a period of inactivity. This inactivity is set for default at 4 weeks. It can be adjusted in the Sensorberg backend if desired.

As our SDKs provide physical access to spaces and we place a high level of importance on security, we want to ensure that inactive/dormant devices are not lying around with access rights.