Open sriGanna opened 3 years ago
In the current approach, we're only planning one extension. For the majority of users, they will not have a Haply or other haptic device, so the haptic portions of the extension must be written to be dormant if not in use. Worst case would be if it had a running loop or something all the time even with no Haply connected, slowing down the browser, reducing laptop battery life, etc.
Currently, we haven't thought through how the applications will be launched. Once launched will the haply code be constantly running in the background or will we need to relaunch with each new rendering? What are the considerations/ ramifications for each approach?