The lib seems to have a better API and I think will be easier to reason about. We also want to probably just use the library directly rather than through something like react-native-cycling-sensors. Then we would just extract the logic for handling data and the different types of sensors (service + characteristics) we support into some utils file.
UX wise we want to change the sensors page to show all devices (those with advertised services matching what we support) and then on connect we would also grab all the characteristics that device has and whack it in a DB table linking to the sensor.
The lib seems to have a better API and I think will be easier to reason about. We also want to probably just use the library directly rather than through something like react-native-cycling-sensors. Then we would just extract the logic for handling data and the different types of sensors (service + characteristics) we support into some utils file.
UX wise we want to change the sensors page to show all devices (those with advertised services matching what we support) and then on connect we would also grab all the characteristics that device has and whack it in a DB table linking to the sensor.