I’m sorry but most of these arguments don’t make much sense to me. As a UI designer, I would always start designing on mobile, and then adjust the design for desktop. The reason is simple and can be explained best with the following analogy:
If you’ve made your life fit in a tiny New York apartment, you’ll have no trouble when you move to a house in the suburbs. But going the other way, from a house full of stuff to a tiny apartment, is much more difficult. Designing for small screens works the same way. (source)
@magicmark said:
- Ease of changing things
- SEO, if your desktop page is poorly designed then Google could drop you
- Low hanging fruit, there’s still 10% of your customers on desktop, every sale/view counts. Don’t ignore them.
- Tablet users, what if they visit on an iPad one day that shows the desktop breakpoint. You could have lost a customer.
- What if the browsing behaviour of the population shifts, a new device is released that takes off (folding tablets for example).
Those arguments assume that there is no desktop version at all, but this has little to do with the question. @chappardababbar’s question is more about wether it would make more sense to start designing on mobile and then adjust for desktop or the other way around (stop me if I understood it wrong).
You can override a desktop style easily on mobile, but going the other way is just insane.
This could have been an argument against “mobile-first” but that is not true. The most famous CSS frameworks like Tailwind CSS for example start from mobile and simply write css the following way, there’s nothing insane about it:
// Styles for mobile here
@media (min-width: 768px) { // Styles for tablet and up here }
@media (min-width: 1024px) { // Styles for desktop and up here }
I tested out Webflow today, and I think it’s good but this “desktop-first” philosophy seems to make the tool much harder to use for experienced designers. I personally wished it would let you choose which way to go on a project-basis. What do you think @magicmark?