5 ms·

The ideal solution is a site or app that works well on both, like how Apple's site works no matter what type of screen you use.

• bigiain 14y ago
  This is how we view the "mobile first" movement - not in terms of first developing a mobile version and then working out later how to turn it into a desktop site, but instead using the laser-like focus that "mobile" requires to properly identify and prioritize your goals. It's much more about getting your design requirements listed in order of importance - if you spend the time thinking about questions like "if I have to fit this product/site/app onto a 4inch diagonal screen, what are the absolutely most important bits to show first?", you'll have a much easier time designing upwards to the tablet/netbook/laptop/desktop sized versions. Shrinking down to a 4" screen from the 1600pixel wide monstrosity that every single stakeholder has insisted has _their_ "critical" piece included is _way_ more work. I've often used the "mobile first" approach to gently encourage clients to prioritize goals properly "I know we're not considering a mobile version of this site at this stage, but there's a _lot_ of conflicting requirements for your homepage here. If we were in the future to develop a mobile version, which of these things would we cut and which would we keep if we only had a phone screen to display everything on?" is an approach thats worked well for me…