nov 7 2014 00:38 Crest Christopher <crestchristop...@gmail.com>:

> Why do you recommend building mobile first ?

The main reason as I see it, is that mobile first methodology forces you to 
take a hard look at your content and prioritize it after what the users 
actually need to see first, second and so on. All fluff has to go for mobile. 
And if it’s fluff why should it stay there for browsers? 

When you do this, you typically will realize that content, its structure and 
presentation is a design problem. Depending on your clients it may also involve 
teaching your them about their content.

It baffles me how little some commercial operations actually know about what 
content their users actually are looking for and when they need it.

Of course, content structure is very much tightly connected to markup, which I 
find many designers take far too lightly as it influences presentation, where 
CSS comes in. So far I’ve broken my wows when doing mobile first by using 
javascript solutions affecting layout and structure. But I have no users on 
mobile that have javascript inactivated (about 5% on desktop).

Anyway, from a CSS design standpoint I too find it more fruitful to do a good 
mobile design and iteratively build on that when targeting larger displays.

______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to