Tags: mobilefirst

Mobile-first and IE8 Solution – Introducing grunt-legacssy (Updated) | Robin Plus

A handy way of automating the creation of old-IE stylesheets using Grunt. This follows on from Jake’s work in using preprocessors and conditional comments to send a different stylesheet to IE8 and below—one that doesn’t contain media queries. It’s a clever way of creating mobile-first responsive sites that still provide large-screen styles to older versions of IE.

APIs First « Just Getting Started

The best “Mobile First” strategy is an “API First” strategy:

“Mobile first” companies really are just a front end selection accessing a solid API driven backend infrastructure.

I think Luke would agree. He built a command line interface for Bagcheck, for example, before there was even a UI—mobile or otherwise.

beta.guardian.co.uk

Those clever chaps at The Guardian are experimenting with some mobile-first responsive design. Here’s how it’s going so far.

The code is on Github.

Twitter without Hashbangs

Remember when I linked to the story of Twitter’s recent redesign of their mobile site and I said it would be great to see it progressively enhanced up to the desktop version? Well, here’s a case study that does just that.

Jordan Moore | Web Design, Northern Ireland, Bangor, Freelance

A sweet little meditation on the nature of the web and responsive design.

Leaving Old Internet Explorer Behind — Joni Korpi

Joni points out a great advantage to the mobile-first approach if you choose not to polyfill for legacy versions of IE: you can go crazy with all sorts of CSS3 goodies in the stylesheet you pull in with media queries.

Athena - MediaWiki

Documentation of an ongoing project to create a mobile-first responsive MediaWiki theme.

#816: Revert mobile-first media queries and remove respond.js - Issues - h5bp/html5-boilerplate - GitHub

This thread on whether HTML5 Boilerplate should include Respond.js by default (and whether the CSS should take a small-screen first approach) nicely summarises the current landscape for web devs: chaotic, confusing …and very, very exciting.