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

Confirmation before actually launching some addictive apps #2597

Closed
1 task done
vatbub opened this issue Feb 12, 2024 · 1 comment
Closed
1 task done

Confirmation before actually launching some addictive apps #2597

vatbub opened this issue Feb 12, 2024 · 1 comment

Comments

@vatbub
Copy link

vatbub commented Feb 12, 2024

Is your feature request related to a problem?

I have recently heard from a friend who uses iOS that there's an app that adds a confirmation dialog before launching some addictive apps (like Instagram or Twitter) to confirm that the user really wants to open this app. The idea is that users usually open these apps out of boredom and sometimes even unconsciously, making users spend lots of useless time in those apps. Introducing such a confirmation forces the user to take a conscious decision to open the app or decide to use his time productively after all.

Describe the solution you'd like

The feature is entirely controlled by the user. The user can therefore specify a list of apps where the feature shall be enabled. For apps with the feature enabled, the launcher shows a confirmation dialog whenever the user wants to open the app, asking the user whether he really wants to open the app.

If the user confirms, the app opens as usual. If he aborts or declines the confirmation, the user returns to the home screen.

In addition to that, some statistics would be nice, but optional:

  • The number of times the confirmation dialog was confirmed (and thus the app was opened)
  • The number of times the confirmation was aborted
  • The approximate time saved by not opening those apps (average time spent in the app per use * times the confirmation dialog was declined)

Feature Request Procedure

@NiagaraSupport
Copy link
Collaborator

Hey there, and thank you for your suggestion.
Something very similar is already planned for the future (see #2407), so I'll go ahead and close this one as a duplicate.

@NiagaraSupport NiagaraSupport closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2024
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