Skip to content

Run on login default state #183

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

Open
Garbee opened this issue Jan 30, 2020 · 0 comments
Open

Run on login default state #183

Garbee opened this issue Jan 30, 2020 · 0 comments
Assignees

Comments

@Garbee
Copy link

Garbee commented Jan 30, 2020

Reference from the explainer:

What would the best default state for the user consent/acknowledge be: checked or unchecked by default?


I strongly feel as if the default state should be unchecked. Just like so many other options, companies, organizations, and certain sets of developers feel their applications are so important you just can't live without them. However for most end users, this only hinders their experiences on the web (look back at Notification API.)

Let's not have the default state for end users be where they need to do more work just to keep their system clean. When more PWAs are around, imagine installing 20 or 30 and they all have this checked by default and the user doesn't read to uncheck it. They then get that many apps auto-starting when they may not have any intent for it to happen.

Please, keep the default off with no option to default to on possible. The only exception I would like, is enterprise installs. If a company is deploying apps to their internal users through Group Policy style methods, they may be able to specify when auto-installing a PWA if it runs on login.

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

No branches or pull requests

4 participants