Improve bluethooth connection and rights request workflow for connected sensing devices (e.g. Polar Verity Sense)

[alireza-dhp]

When running the app on iOS for the first time,before logging via a token a popup message appears, requesting permission to use Bluetooth.

Upon denying the Bluetooth permission request, and after enter the token and accept the concept, the app encounters a failure and cannot proceed.

[smeddinck]

alsp improve the Polar integration interface in the Mobile App with all the error handling and proper feedback

may be important to implement better temporary locking in in the user interface, implement connection dialogue as a popup and also possibly integrate documentation for manual workarounds (e.g. connecting devices via system settings and only THEN adding them in MORE)

[smeddinck]

Issues also exist in Android!

[andresgruber]

Describe the different cases @alireza-dhp :

• improve first connection with the polar verity sense
• keep the collection alive - especially during a observation
• provide proper methods of reconnection

[smeddinck]

1. Initial connection needs to make sure that appropriate OS rights requests are made. This procedure should be a triggerable process, since it can then be used for a "manual reconnect" procedure as a last-resort repair mechanism following programmatic and/or manual unlinking as much as possible (see below). The workflow and status signaling must be very clear to users and they should not be able to issue multiple simultaneous connection requests.
2. If we are in a known observation period, i.e. data capture is expected to be active and the BT connection live, but it is not live, or no data is incoming: programmatic reconnect procedure in the background.
3. After N automatic reconnects and/or X duration of "expected data not incoming" (best to keep such variables in config files), trigger a manual reconnect procedure as a last resort (include clear instructions to users).

[ja-fra]

We suggest the following workflow to handle the connections to external devices (Polar):

1. On study-signup we offer to connect external devices on the "External Devices"-screen (if required by the study, as it is currently implemented)
2. If the participant does not connect a device, the affected observations are marked with a ⚠-Icon
3. Additionally, we'll show a ⚠-message on the top of the Dashboard.
4. Both ⚠ take the participant to the "External Devices"-screen
5. When an observation starts (should start) the app tries to (re-)connect to the external device. If this fails, the app will send a notification to the user.
6. When the device disconnects while the observation is running, the app internally tries to reconnect. If this fails, the app will send a notification to the user.

[andresgruber]

Improvements for bluetooth connection with Polar MORE-200

Primary use cases positively tested with App version 4.0.10 on iOS 17.5.1 (iPhoneSE)

• First (clean) installation of the APP, bluetooth is on, polar is off -> login to a study with (hidden) polar observation -> after consent screen the devices screen opens with missing polar -> one can switch on polar and add to devices -> data fetch starts as soon as the observation starts (or has already started)

• Manually stopping polar, while polar observation is running and app is in foreground or background -> notification sent to notification tab and error button appears on dashboard -> shows reason for the error -> sends one to the devices screen -> switching on polar automatically reconnects the polar device and resumes in collecting data

• Manually stopping bluetooth, while polar observation is running and app is in foreground or background -> notification sent to notification tab and error button appears on dashboard -> shows reasons for the error (bluetooth and polar) -> sends on to the devices connection screen -> switching on bluetooth reconnects the polar device and resumes in collecting data

• Manually stopping bluetooth and polar, while polar observation is running and app is in foreground or background -> notification sent to notification tab and error button appears on dashboard -> shows reasons for the error (bluetooth and polar) -> sends on to the devices connection screen -> switching on bluetooth -> screen stays and asks for polar -> switching on polar automatically reconnects the polar device and resumes in collecting data

Other cases positively tested

• App is already installed and has been used, bluetooth is on, polar is on -> App closed and opened again -> Login with a new user > Polar gets automatically connected and starts collecting data

Cases with remaining issues or known limitations

• App is already installed and has been used, bluetooth is on, polar is off -> App closed and opened again -> Login with a new user -> No notification nor error button appears -> closing the app and reopening solves the issue > switching on the polar devices -> does not automatically reconnect -> manually connecting the device is necessary -> collecting data resumes.
• There will be no notification if the app is closed in case polar is disconnected.

[alireza-dhp]

Dear @andresgruber,

I have tested the improvements made to the Bluetooth connection and found that it works significantly better than before. Thank you for the enhancements.

• Devices used for testing:
  • iPhone SE (2nd generation), iOS version 17.5.1
  • Google Pixel 3a XL, Android version 12

There are some issues that I observed:

• iOS and Android:

  • Data capturing does not start automatically when the app is running in the foreground/background and the Polar device is connected. Instead, automatic data capturing only begins immediately after a successful connection to the Polar device. So, if there is an upcoming polar observation and the participant connects the Polar device, data capturing does not start automatically, and the participant must initiate it manually. If this is intended behavior, why is it necessary to connect the Polar device immediately after signing up the participant?
  • The device connection error message should not appear when there are no upcoming Polar observations scheduled.

• Android:

  • It would be better to anchor the capture data button and error message label to the bottom of the page.

• iOS:

  • The error message is unreadable on the Polar observation page.
  • Sometimes the error message is displayed even when the device is connected.