Mobile vs. desktop thoughts ...
Hmm ... not sure where to ask this, so please remove or replace this thought experiment if it doesn't belong on this channel.
Kevin talks alot about fixing/doing up mobile layout first and then going on to desktop layout. With the advent of auto-fit/fill and minmax usage in grid, does this always has to be the case? With basic designs like the CRL Flexbox challenge 4, all sections could be placed in a main grid, and all the content within each section could be nested grids, all with an auto-fit/fill and minmax. That would automatically make it responsive and stack the content as normal in mobile layout.
4 Replies
mobile or desktop first is mostly a preference, and sometimes depends on what site you're making
That's obviously the best answer, hehe.
It's just nice to know that with some of the newer intrinsic design tools, braking points and
@media aren't so scary anymore ...Two of the main reasons mobile-first is talked about as the preferred starting point is:
1) Mobile usage is only growing. More and more people use phones and tablets for their primary browsing experience.
2) Mobile has less screen real estate, meaning that as your site "grows" to desktop you can easily add more stuff. "Shrinking down" from desktop to mobile means trying to figure out what to remove.
While point 2 may seem like it's the same thing, designing with initial constraints is easier for most people and adding feels better than removing.
My preference is design desktop first and code mobile first. If you separate the design and code phases, you can figure out a bunch of stuff that will not be needed for media queries. But, when you do the code, it's much easier to start with mobile code, and make it work there first, then larger