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

Inconsistent with familiar user experience #3

Closed
emouawad opened this issue Apr 21, 2016 · 2 comments
Closed

Inconsistent with familiar user experience #3

emouawad opened this issue Apr 21, 2016 · 2 comments
Labels

Comments

@emouawad
Copy link

Of course this is a familiar user experience on Facebook:
While the difference is small - it is important
in this control user has to:

  • click once to activate view
  • click a second time to pick emoji
    While on FB user (long presses) once and immediately the toolbar is activated and shown
    I believe as an alternative implementation a long press event is more familiar.
@lojals
Copy link
Owner

lojals commented May 5, 2016

This control is actually using one tap por single action as Facebook like, and Long Tap to open the Reactions bar. Facebook just have those events not two clicks as you mentioned. The real issue is that in my version the user doesn't have control automatically from the Touch Begin Method, because is a different view.

@lojals lojals added the wontfix label May 5, 2016
@lojals lojals closed this as completed May 5, 2016
@emouawad
Copy link
Author

emouawad commented May 9, 2016

I believe you misunderstood what i was trying to describe.
I was trying to describe exactly the related open issue titled "selectedOption never get called #4"
Apparently it's a popular request ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants