Responsive vs Mobile Apps

The Internet’s future is mobile.

EthanMarcotteHowever, why is usability guru, Jakob Nielsen, arguing for a move back to separate mobile sites ?
 
Maybe he doesn’t understand Responsive Web Design.
 
To be fair, this year even web developers in 2012 have been falling out of love with RWD (Responsive Web Design).

The benefit of RWD

Pioneered by Ethan Marcotte(pictured above), this coding technique allows content to display in a variety of ways, depending on screen size.
 
Jakob’s main argument is that, whilst RWD allows you to change how the content looks, you can’t change what the content is. Or can you?

FAO Jakob: Responsive Design Lesson 1

Check this out Jak:   Element{display:none;}
 
You can chose to show or hide any element of a web page for any particular screen size you want. Just give it a class or ID.

  1. Want to hide a particular menu item? You can!
  2. Want to display something only on mobile? No problem.
  3. You can even shorten an article or post if you want.

Updating Content

This may be why Jakob has failed to stop developers building sites with RWD. Content is updated in one place, rather than having to update on a mobile app and a ‘full’ site.
 
We are still learning how best to present mobile content (this site is still at beta test stage for mobile), but as James Dyson said, if you work hard enough you can master anything in 6 months. So, by January 2013, I should be able to walk the walk!
 
Creating mobile sites is the most challenging and therefore exciting aspect of web design right now. For me, RWD seems to hold all the answers… or am I missing something ?

2015-12-13T20:57:26+00:00 Geeky Tips|