You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo
I still think this issue should be opened here
Report
When first starting the application, it instantly asks for permission to send notifications. See the screenshot below.
There is no explanation as to why this permission is needed and the user has not even had a chance to try the application yet. But if they decline it, then the node will not run in the background. Let's add a permission info screen to the onboarding flow, right after we tell them we're not about to start the IBD. They will then have the proper context to make an informed decision. See the designs below.
The text was updated successfully, but these errors were encountered:
Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo
Report
When first starting the application, it instantly asks for permission to send notifications. See the screenshot below.
There is no explanation as to why this permission is needed and the user has not even had a chance to try the application yet. But if they decline it, then the node will not run in the background. Let's add a permission info screen to the onboarding flow, right after we tell them we're not about to start the IBD. They will then have the proper context to make an informed decision. See the designs below.
The text was updated successfully, but these errors were encountered: