-
Notifications
You must be signed in to change notification settings - Fork 34
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
UI on the permissions page #919
Comments
One of the programs generated an instruction manual - it's a word doc and contains program specific information so I am not uploading it here but sending it directly to @Abby-Wheelis. It might be worthwhile to explore how we can walk people through step-by-step in the redesigned screen. |
Were we going to consider this - some kind of "wizard" view? Would having one permission on one "page" seems to be pretty standard for new phone onboarding, at least. But I'm not sure if it will make things too complicated for the number of permissions that we need |
With a tutorial type view here, I think if we have to show users how to use it, then the page needs to be redesigned more. I think all we'd need to convey is "if it's red click the fix button and follow the instructions", right? I'm hoping that getting rid of the multi-dropdown configuration and isolating the explanations to their own Modal (with a clear way to access it at the top, maintaining transparency) will make the screen simple enough to lead users to the conclusion of "if it's red click fix" on their own. I also wonder if the actual device settings pages are something that's tripping up users just as much, at least in some cases it takes you to a page in the device settings, and you kind of have to know what to do from there. Examples off the top of my head would be in iOS you get dropped in the app permissions, but then you have to click locations, then, always, and toggle on precise. Android to turn off optimizations sometimes I've had to change a dropdown to not optimized, then scroll a while... I can see where this could get confusing and/or burdensome ... if we could "wizard" there and show users how to fix things in their device's settings that would be pretty magical, but this would differ per device and OS and I'm not sure iOS or Android would let us control the screen outside of our own app. Best case scenario I think would be that every permission "fix" would just be a popup where they have to click "allow", but not sure to what extent that's in our control. |
Yeah, woudn't that be great! That is what it used to be back in the old days. In fact in the super old days, on android, the permissions were listed in the app store page, and you didn't have any dynamic popups. But the platforms have slowly been cracking down on this - they want to add more friction so that the user has to really really want this functionality to turn it on. See discussion around the optimization screen in particular in the API upgrade issue (#934 (comment)) Having said that, if you can come up with alternatives (e.g. |
I do think this is achievable. Other apps manage to get the permissions they need without making users dig around in any system settings pages -- even apps that have similarly extensive background services and location permission requirements. |
The onboarding changes have now been merged into production, and updates like battery optimizations and location permissions are decreasing the barriers to install by adding popups where users used to have to navigate through complex settings. |
I've had the chance to help a few users through the initial hurdle of getting permissions enabled, and noted a few themes that we should keep in mind when we next update that page:
1 and 2 could potentially be addressed by re-wording or adding to the statements to the user
3 was addressed already here: 5b3dc298ff0194983691af40e585db7e1156b9fb
All are good to keep in mind as we soon update the page and potentially find ways to configure the UI in a way that "fixing" the issues and clearing the page is as intuitive and pain-free as possible, letting people access the app!
One idea I'd had was a popup of some sort that could be presented upon entering the page and then accessed again from some button, acting as a "tutorial" or "instructions" page guiding the user. The use of something that is shown and hidden would allow for detailed instructions to be referenced as needed without cluttering the page itself.
The text was updated successfully, but these errors were encountered: