Lessons learnt making our web app responsive (opens in new tab)

Maybe you could apply those lessons to this blog entry so I can read it on my phone without a giant blue bar taking over the entire left side of the screen...

The more and more I get to develop sites for people in the wild, rather than corporate intranets, the more I learn: truly semantic HTML is responsive by default.

You have to go out of your way to make it unresponsive. You have to insist that you know the one, true, best way to use your site for every type of user--big-screens and small, strong- and weak- and no-sighted, color-seeing and non-color-seeing, rich-enough-to-own-the-latest-macbook or not. The pixel-perfect positioning of your logo is more important than people who do not meet your conception of your perfect user.

Sure, certain concessions need to be made. Obviously, if you're making a shape-matching game, the blind need not apply. Deaf users probably won't get anything out of SoundCloud. But most sites have a broken interface for anyone other than a median human.

Just imagine if HN had a properly semantic HTML layout. It'd scale properly to every cellphone with a browser, ever. Unstyled, semantic HTML may not be pretty, but it works. Resist the temptation to corrupt it with CSS and its nutty notion that it could ever maintain cross-compatibility with print.

Really really vapid 'article'. It's kind of empty of any real content which indicates to me some kind of voting ring or manipulation seeing this so high on the front page.

Akin to a "lessons learnt writing great software".

"Test on different operating systems." "Run profiling to detect memory leaks" "Don't commit buggy code."

Just some obvious guidelines anybody would know.

I always wonder if it is better to just leave sites as unresponsive if you've already skipped designing for mobile. Honestly vanilla non-responsive sites, without too many bells and whistles (hover/flash stuff) are easier to navigate than a poor mobile site (or even a mediocre one). I know what to expect when I click something, and even if I have to zoom in on my own, I still would rather have the actions be consistent with the desktop version than be poking around looking for the menu.

Next in the series: "Lessons in server capacity learnt when we got more traffic than usual". The page doesn't load for me.

As an amusing aside "dom kop" (same phonetic as their domain name) in Dutch or Afrikaans translates to "stupid head"

This is what I see on my iPad. http://imgur.com/3y4zpXT

I guess there's a seventh lesson they still haven't learnt yet.

Taking a look at the web app I think the time would've been much better spent by improving the interface for desktop users. It's extremely unintuitive, several columns just show up blank for me (which I initially thought was a bug) and the top menu bar is duplicated (on the left and on the top.)

Also, in Dutch your site sounds like "stupid head" (domcop, pronounced out loud, sounds like dom kop.)

Learning about responsive design means more than learning to use the bootstrap grid . Sure,the grid system is great and works in many cases . However, there comes a time when your websites will hurt if you don't truly understand the fundamentals of responsive design .

Buying a Bootstrap theme isn't very impressive. Try formatting images, videos, rescaling fonts across devices. It will take a lot more than two weeks.

Yup, still some more lessons to learn here.

Go irony!

True, but responsiveness is totally worth it. For example British "Metro" magazine, just by making it's website responsive increased the traffic from the social networks by 100%. Also there is no hustle with m.domain optimisation.