First, I agree that “mobile first” as an exclusive strategy is not appropriate for all projects/apps/services/clients.
IMO there are lots of benefits to “mobile first” other than just the emphasis of mobile devices. Designing for the small viewport first is still my preferred approach (without considering smartphones specifically).
When I pitch it to people, I often focus on the benefits to designers (by forcing us to prioritize content layers in a constrained viewport) and on the benefits to engineers (by getting the markup correctly ordered before going desktop; not having to edit it as much later).
In other words, “mobile” can be a misnomer.
Maybe I've misinterpreted what "mobile first" actually means, but I thought it was simply a strategy to prioritize content and create strong hierarchies across all screen sizes.
I am reading this article on a 13 inch screen. There is 2606 pixels of stuff above the content. That’s a lot of scrolling.
I’d love to hear people’s thoughts here. Does this hold true for what you design and build? Are you a mobile driven business contemplating building a web app for larger screens?
I agree with ”focusing on what Jobs your users are trying to do”.