Introduction
This article is very personal to me, for a lot of reasons. One of which is that when I first got into web development, this was the bane of my existence. I would spend time mulling this over before I basically started any design. This was of course before I started using friendlier CSS frameworks like TailwindCSS and Bootstrap.
I have a personal belief that the choice to start with either mobile or desktop is dependent on the learning trajectory you followed, or the tutor/instructor you learned from.
If you learn from an instructor who develops mobile-first, you are more likely to follow this pattern and vice versa.
However, I decided to do a little bit more research about this, and show the two sides of the coin, so that everyone is aware of where they are standing.
Overview
Mobile-first and desktop-first development are two approaches to designing and building web applications. Each approach has its own advantages and disadvantages, and the choice between them depends on the specific project requirements and target audience.
Mobile-first
Mobile-first development involves designing and building the mobile version of a website or application first and then expanding it to the desktop version. This approach prioritizes the needs of mobile users, who are becoming increasingly important as more people access the internet on mobile devices. Mobile-first development often focuses on simplicity, speed, and usability, which can lead to a better user experience on all devices.
Advantages:
- Prioritizes the needs of mobile users, who are becoming increasingly important.
- Focuses on simplicity, speed, and usability, which can lead to a better user experience on all devices.
- Helps developers to create a responsive design that adapts well to different screen sizes.
Disadvantages:
- May neglect certain desktop-specific features, such as hover effects or complex interactions.
- Can be challenging to scale up to larger screens, as the design may not have been intended for them.
Desktop-first
Desktop-first development, on the other hand, involves designing and building the desktop version of a website or application first and then optimizing it for mobile devices. This approach has traditionally been the standard, as desktop computers were the primary way people accessed the internet. Desktop-first development often focuses on visual design, advanced functionality, and larger screens, which can lead to a richer user experience on desktops but can be more challenging to translate to mobile devices.
Advantages:
- Allows for more advanced functionality, larger screens, and richer visuals.
- Provides developers with more design flexibility and opportunities for creativity.
- May better support desktop-specific features, such as hover effects or complex interactions.
Disadvantages:
- May not provide an optimal user experience on mobile devices.
- Can be more challenging to create a responsive design that adapts well to different screen sizes.
- May neglect the needs of mobile users, who are becoming increasingly important.
Conclusion
In summary, the choice between mobile-first and desktop-first development depends on the specific project requirements and target audience. However, as more and more people use mobile devices to access the internet, mobile-first development is becoming increasingly popular and important.
Disclaimer:
The bulk of this article was developed by chatGPT, although the experiences remain mine, and the personal experiences as well. But, yeah, #ABotWroteThis...In a way.
cheers
Top comments (4)
Personally, I don't see why either one should be "first". Why not take into account all users equally?
You can do this when you are using css frameworks like tailwindCSS or bootstrap.
But using normal CSS, its a bit of a difficult thing to do. This is because naturally, you have to start your design from somewhere.
Hey, this article seems like it may have been generated with the assistance of ChatGPT.
We allow our community members to use AI assistance when writing articles as long as they abide by our guidelines. Could you review the guidelines and edit your post to add a disclaimer?
Guidelines for AI-assisted Articles on DEV
Erin Bensinger for The DEV Team ・ Dec 19 '22 ・ 4 min read
Thanks a lot for bringing this to my notice. I have made the necessary modifications.