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

limit unglue notification #627

Closed
matkoniecz opened this issue Oct 2, 2017 · 7 comments
Closed

limit unglue notification #627

matkoniecz opened this issue Oct 2, 2017 · 7 comments
Assignees
Labels
feedback required more info is needed, issue will be likely closed if it is not provided

Comments

@matkoniecz
Copy link
Member

Hint introduced by 361fee9 is shown over and over again

Maybe after displaying it for example 2 times it should not appear anymore? Or at least appear rarely?

@westnordost
Copy link
Member

westnordost commented Oct 2, 2017

I am open for suggestions on that logic.

@westnordost westnordost added the feedback required more info is needed, issue will be likely closed if it is not provided label Oct 2, 2017
@matkoniecz
Copy link
Member Author

For experienced users this notification is not necessary (but given that I maintain my own fork I am an extreme outlier, the same applies for nearly everybody active on the issue tracker), so I think that this addition makes sense.

Showing it only once would be not enough - people on first contact with a software sometimes dismiss explanation and later would like to see it again.

Showing it once and adding "show again are already displayed hints" setting is a solution that I like but I know that one of design decisions is to avoid settings.

Maybe showing it three times and reset this counter if app was unused for longer than 20 days (inspired by how Firefox behaves)?

I would recommend just "show it three times and never again" if counting inactivity time is an overkill (though I think that it would be again useful once other hints are introduced).

@antonv6
Copy link
Contributor

antonv6 commented Oct 6, 2017

Maybe not strictly related to this issue, but what's the idea behind tapping a button being the only way to unglue the map?

If users were allowed to just drag the map to unglue it, there wouldn't be any need to show this notification at all, and it also would make UI feel more familiar. Many, many apps that have a map just allow users to drag it around by default, and then have a button to show or follow their location. Such a button doesn't need any notifications, sometimes doesn't even have a tooltip, because it's instantly discovered when people want to see their location, and the other two buttons are just + and -.

@westnordost
Copy link
Member

  1. It was a feature request not to turn off follow-me-mode when answering a quest and to make follow-me-mode more sticky in general (New feature: Stick to GPS #429). Answering a quest involves clicking on the marker, which the map registers already as a swipe and thus turning off the follow-me-mode. While this particular behavior may or may not be considered as a bug of tangram-es, in any case, just swiping the map by one pixel would already turn off the follow-me-mode, which made that mode too volatile. To disable the mode with a "strong swipe" would also have been conceptually possible, only not technically (I think). However, there is a second reason:
  2. Following the position is supposed to be the default, because the user should be discouraged to answer quests that are not at his location. The non-follow-mode is just there to "look around".

@matkoniecz
Copy link
Member Author

The non-follow-mode is just there to "look around".

And for situations when GPS is showing wrong position

@matkoniecz
Copy link
Member Author

It was reverted in c69046a

Is it because "show info X times then stop doing this" is a bad idea? Or is it a bad idea just in this case because interface is too tricky and without this message many users are confused?

@westnordost
Copy link
Member

westnordost commented Jan 21, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback required more info is needed, issue will be likely closed if it is not provided
Projects
None yet
Development

No branches or pull requests

3 participants