-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add brief explanation to Nearby Places UI #706
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
Comments
If the explanation text is short enough, we could fit it below the "Nearby Places" text in the actionbar, just like the number of uploads are shown in the home screen below the "My Recent Uploads" text in the actionbar. Or we could use something like a tooltip that would come up only the first time the user ends up on the screen. |
Yeah, text in the actionbar sounds feasible to me (it could say just "nearby places that lack photos", perhaps?). But not sure if that is in line with UI design guidelines. Hopefully someone experienced in UI design can chime in? The first-time tooltip is a viable idea also. :) |
Just attaching a screenshot for reference as to what it could look like: I have used this library for the tooltip. |
Given the wide variations in screen sizes, we cant guarantee that the message in the toolbar will be fully visible. I think the screenshot is an example of this. If we're shooting for a "first run" type of experience, would it be better to use a library like MaterialShowcaseView and walk the user through the functionality, highlighting that you can switch between map and list views, and what the screen is all about? |
Thumbs up from me for MaterialShowcaseView. :) Not sure how time-consuming it is to implement, but it does seem like the ideal solution. |
MaterialShowcaseView looks neat. We could start by using it for NearbyActivity first and probably implement it for other screens as well in time. |
I think it currently isn't very clear to a lot of users what Nearby Places does, and there isn't space in the action bar to make the title more explicit. Perhaps we could have an additional UI component (like a subtitle) to explain the feature?
The text was updated successfully, but these errors were encountered: