Why Responsive Design Sucks
blog.raavel.com
Why Responsive Design Sucks
1–7 of 7 posts
Re: Why Responsive Design Sucks
#2(#3 Is a huge pet peeve of mine)
I fear too many designers only "test" the mobile site; they don't actually "use" it. Using and testing are two vastly different things as the former actually puts you into the driver's seat for a ride from the visitor's (read: customer's) perspective. Until that happens, designers are only engaging in speculative design that they think is responsive. It's not quite the same.
All the problems highlighted shouldn't be happening on a properly designed and architected site.
Re: Why Responsive Design Sucks
#3Re: Why Responsive Design Sucks
#4Re: Why Responsive Design Sucks
#5Responsive design is not simply 'download everything, show less on smaller screens'. If your version of responsive design sounds like this, then you're doing it wrong.
Responsive design means taking into account the form factor of the device, and tailoring the layout / positioning etc in accordance. This may mean hiding links and buttons behind some extra drop-down menu or something similar, but you shouldn't be simply hiding things that the user is suddenly not allowed to view.
Additionally, if making your site responsive adds so much extra crap that your 'responsive' version loads noticeably slower than the non-responsive version, then I'm going to hazard a guess and say that your original design is also bad.