Goodbye to 8 Design Elements: Dropdown, Carousel, ...
uxmag.com
uxmag.com
First of all I wouldn't classify a web page as a design element. Secondly they aren't going anywhere. There are valid reasons for lots of sites to switch to an app approach but web pages are still very useful and I don't see that changing.
To be even more effective, you can make it so that the application is only loaded once and the data is be retrieved when needed, optimizing the use of the network. I would go even farther: I think that, at some point, a lot of applications will be using a common base for retrieving and displaying the data from the network. It may be a little avant-guarde, but it would be great to have a single application that would handle the content from all application. I know it's just science-fiction, but wouldn't that be great?
- "colo" is not really about sharing a server but about being in the same data center.
- cloud is almost by definition a "shared-resources" hosting: you run a VM on a physical server that is shared with others VMs, therefore you are still subject to noisy neighbors.
- shared hosting is not only about resources but also about services and ease of use.
I see misconceptions and shortcuts for every point in the article, I hope it won't stay long on the frontpage.
Aside from the fact that we haven't figured out the SEO yet ( see https://sourcegraph.com/blog/switching-from-angularjs-to-ser... ), encouraging the unwashed masses to "appify" their content is tantamount to malpractice IMO.
Every time I've done analytics on a carousel (say a carousel with 3 choices, A, B and C), I run a test: A vs B vs C vs Carousel(A,B,C). The Carousel has never won.
There is a very simple reason why. The user doesn't see "oh cool, a carousel, let me wait for it to spin around." They see A, B or C at random. As a result, their conversion rate is the average of the conversion rates of A, B and C.
Supporting multiple browsers... gone! If it works in Chrome... done.
Responsive design? Gone! We're post-PC now. Design for Android phones only.
Design? Boom! Gone. Text only. Chrome gets in the way.
Color? Clutter. Let the user choose their system palette. Green text on black by default.
Boom. Sorted.
Mouse-over to reveal functionality doesn't work for touch.
There's plenty more wrong with this article, but I thought I'd clear up this particular piss-poor communication item.
Don't (some) mobile devices trigger :hover states when elements are tapped on? If they don't, surely there's JS to fix that; and then users with a mouse can enjoy their agility, while mobile users have to make an extra tap. And you'll be happy to not have simply thrown it all away, too, when pixel-perfect gaze tracking finally gets invented.
> 6. Web Pages
Hang on there. The ability to bookmark and share links to individual sections is super important, it's what makes "Hyper Text" "hyper". "go to URL and then do X, Y and Z" won't fly, neither will being unable to restart your browser and continuing where you left off. But if you update the URL to reflect that current state, you kind of still have web pages, you see? It doesn't matter how shiny they are or how you transition them, they'll still be web pages. Not that there is anything wrong with that.
We already had Flash, long before Javascript could do much, and we already had attempts at quite elaborate and artistic websites, complete with intro and sections folding and fading and morphing - and even the good ones sucked from a "web" perspective. Good for viral marketing, annoying or even useless for extended use.
Deleted comment
I wouldn't be so quick to judge somebody by their hobbies. How about judging him based on his work? http://www.asheavenue.com/