Go nuts with CSS3 hover effects
tympanus.net
Go nuts with CSS3 hover effects
1–10 of 70 posts
Re: Go nuts with CSS3 hover effects
#2Re: Go nuts with CSS3 hover effects
#3Re: Go nuts with CSS3 hover effects
#4When the iPhone was released I thought it would be the end of hover. I know that's what I think about when I see something like a menu which only works on hover.
If developers chose to use stuff on the basis of what they as developers think should be used - and if that meant iphone users couldn't use them - guess who would ultimately win that battle? Not Apple.
IE would have died years ago if developers had adopted that culture en masse.
Re: Go nuts with CSS3 hover effects
#5Re: Go nuts with CSS3 hover effects
#6When the iPhone was released I thought it would be the end of hover. I know that's what I think about when I see something like a menu which only works on hover.
Always surprises me that developers let platform makers dictate what they can use and what they can't. If developers chose to use stuff on the basis of what they as developers think should be used - and if that meant iphone users couldn't use them - guess who would ultimately win that battle? Not Apple. IE would have died years ago if developers had adopted that culture en masse.
Also, it's easy to add a touch event to do the same as the hover event, it's up to developers to do it. I was just thinking about the dependency of hover which need to go.
Re: Go nuts with CSS3 hover effects
#7The animation effect is more garish than anything, but this is a probably a personal quibble. It takes 200 ms for the hover effects to finish loading. I'd rather have the hover transition instantly, so I can spend less of my life watching text fade in.
The Chrome Web Store uses this to excess, with sliding panes flying everywhere. It looks great, but it's really painful to use.
Re: Go nuts with CSS3 hover effects
#8Earlier quoted context omitted.
Always surprises me that developers let platform makers dictate what they can use and what they can't. If developers chose to use stuff on the basis of what they as developers think should be used - and if that meant iphone users couldn't use them - guess who would ultimately win that battle? Not Apple. IE would have died years ago if developers had adopted that culture en masse.
That would be right if this was about platforms but it's not, it's about interaction. If you can't hover then why depend on it? Also, it's easy to add a touch event to do the same as the hover event, it's up to developers to do it. I was just thinking about the dependency of hover which need to go.
The thing I don't like about hover is that at core, it's a leap of faith -- you're asking your user to mouse around blindly (like Myst, anyone remember that frustration?) until the page rewards their fumbling with some sort of UI treat. It's a symptom of inefficient and poor design.
(Having said that, these are lovely animations.)
Re: Go nuts with CSS3 hover effects
#9Usability vs cool UI is always a tough one. The ones who can do both at the same time are geniuses. That's why Apple is always on top.