Investigate Options for Comport Selection

[sriGanna]

Currently, both web serial and web Bluetooth require the user to specify the comport for each page that is being used. This is presented as a browser popup.

We need someone to investigate if there is a way to cache the comport info or if the user needs to go through the process for each image.

[jeffbl]

This would not gate restricted beta (which does not have any haptics rollout to end users), but I'd argue this may be complicated, so best to do development work on it earlier rather than later. However, if you think should be slipped out in favor of other more pressing items for getting a compelling haptic user experience implemented, please ping me.

[rayanisran]

We're dedicating our efforts towards getting a first implementation of the audio-haptics experience into the architecture within the month, so I'm in favor of pushing this back for later.

[sriGanna]

We're dedicating our efforts towards getting a first implementation of the audio-haptics experience into the architecture within the month, so I'm in favor of pushing this back for later.

agreed with this. @jeffbl based on that would it be possible to push it out of the Jan 14th column on the project board?