• Thomas Michael SemmlerThomas Michael Semmler, 4 years ago

    Can we please start to acknowledge that this is spam at this point?

    9 points
    • Duke CavinskiDuke Cavinski, 4 years ago

      hey don't make anthony mad, he is a master ux specialist and we plebes merely tremble in his shadow. he's spent three thousand years exploring the annals of the Temple of User Delight and has humbly brought his findings for our mere enlightenment.

      3 points
  • Jakub FoglarJakub Foglar, 4 years ago

    I’m assuming the article is about design choices, not about the technicality of implementing pressed-down states, because that one is solved (as Marc pointed out).

    You are yet again presenting your opinions as facts.

    The hover effect for mobile buttons is a ripple effect.It’s important to convert your desktop hover effects to mobile ripple effects

    Who says that? :D

    I could give a counter argument. If the user sees the whole button darken while they are pressing down on a part of it, it’s clear what they are actually pressing. If they see your ripple effect, they could assume that this effect is just a visual representation of where they tapped on the screen, and that it could happen regardless if it’s a button or not.

    3 points
    • Andrew C, 4 years ago

      Let’s put aside the obvious fact that the on hover mobile “problem” has several workarounds (focus, active and blur states in addition to the ontouch event mentioned earlier). Lets sidestep that obvious fake problem.

      Logically if a button press “didn’t work” why would a user care what kind of feedback was given? Nothing happening IS the feedback. And if it did work they’d receive a state change of the page as feedback. It’s clear these articles have been written with no tests done to substantiate anything.

      1 point
  • Marc EdwardsMarc Edwards, 4 years ago

    Using a hover effect on mobile apps causes buttons to stay stuck in the hovered state when tapped.

    ontouchstart="" can be used to get :active working.


    3 points
  • Liam FLiam F, 4 years ago

    This topic could have explored so much more than finding one codepen and writing around that. The codepen is a cool mimic of the material design for buttons, but this article writes as if this is the standard way of pressed (not hover) states for buttons. Which it ain't.

    This site in general feels like a dark pattern, an opinion blog disguised as UX research and findings.

    The about page mentions articles being written with research but when asked about this you tell readers...

    My claim comes from years of experience working with users and clients. If you need research to verify a claim you have doubts about, you should go do research on it.

    2 points
  • Alex MarinAlex Marin, 4 years ago

    I can speak with confidence because I understand all the principles involved. I think you mean to say that you yourself can’t speak with such confidence because you don’t have a full understanding, so allow me to elaborate.

    This fucking guy...

    1 point