Be nice. Or else.
Design/Dev Joined almost 4 years ago
Beautiful design ruined by scroll-hacking. It drives me insane to have to scroll and scroll and scroll for nothing to happen. Use arrow keys or buttons or anything else – just let me scroll normally.
I think it's less a global convention and more of an app-scoped pattern.
Facebook for example subscribes to click-to-open, but they have one area in their Events section that has an on-hover dropdown. It's pretty jarring.
If your app has a lot of menus, then on-hover may save the user countless clicks. My dentist's software, I noticed, had large icons that, when hovered, displayed a giant menu. Seemed perfect for the situation.
Personally, activating panels on-hover doesn't make as much intuitive sense as on-click. Typically items in a dropdown menu are contextual, supplementary, or tools – all of which require user intent to discover. An errant hover does not convey enough intent for me to think the user wants to see what's behind the little down-arrow. A click does.
Consistency either way is probably the best bet.
Dribbble bought Crew back in April and shows no sign of financial troubles. What are you seeing that makes you think it's a "dying platform?"
In my state there are hundreds of thousands using internet that’s spotty at best. Sub-1mbs connections that are often blanket rural wifi or satellite (high latency).
By using a service worker and an app frame, you can cache the critical aspects of the site, including content, upon initial load which allows the user to go on browsing even if their connection is weak.
And it doesn’t specifically cater to those with that need, it makes for a much faster browsing experience even for modern connections. I’ve seen studies showing that for every half-second decrease in perceived load time, revenue goes up 7%.
All this being said, do what makes sense for the situation. If a brochure site can do its job as a one page HTML doc and you see no benefit to the extra overhead, then it’s no skin from anyone’s back. PWA tech is still being figured out and most browsers don’t support a lot of the requirements.
I hope that PWA tech starts to become easy enough to handle in order to become ubiquitous, but for now the answer really depends on your audience. A PWA can prove "worth it" for audiences with spotty internet connections (offline mode with service workers) and/or for audiences with modern browsers.
In my opinion, PWAs are the future of the web – an app that lives at a URL instead of on your phone, essentially, and blurs the lines of what's "native." Servers are more and more often serving only data via an API as opposed to rendered HTML files which leads to less bandwidth used and a faster experience.
Very refreshing. No scroll-jacking, nice information hierarchy, all relevant information present. Rare these days.
Check out pwa.rocks.
God, this trend of purposefully making websites difficult to use can't go away soon enough. A plain HTML document would be more useful and be easier to understand.
I love Numi, but I've been using it a lot less since finding out you can do math in the Sketch App width and height inputs.
Thanks Luc, I'm checking it out now.
Be nice. Or else.
Designer News is a large, global community of people working or interested in design and technology.