Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate whether UI should be constantly running in the background or not? #21

Open
sriGanna opened this issue Sep 8, 2021 · 1 comment

Comments

@sriGanna
Copy link
Collaborator

sriGanna commented Sep 8, 2021

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?

@sriGanna sriGanna changed the title Investigate whether UI is constantly running the background or not? Investigate whether UI should be constantly running in the background or not? Sep 8, 2021
@jeffbl
Copy link
Member

jeffbl commented Sep 8, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants