I'm a Systems Reliability and DevOps engineer for Netdata Inc. When not working, I enjoy studying linguistics and history, playing video games, and cooking all kinds of international cuisine.
Not sure if this is true for everyone, but I've consistently found it easier to start with a compact layout for mobile, and expand from there to larger layouts for other devices than to go the other way. So, if you design for mobile first, you might find it easier when you have to expand to larger displays. The caveat is that you have to be a bit more conscious as you scale up about how things look on really big screens (a layout made for a FHD screen size first is more likely to scale well to QHD than one made for a much smaller screen first).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not sure if this is true for everyone, but I've consistently found it easier to start with a compact layout for mobile, and expand from there to larger layouts for other devices than to go the other way. So, if you design for mobile first, you might find it easier when you have to expand to larger displays. The caveat is that you have to be a bit more conscious as you scale up about how things look on really big screens (a layout made for a FHD screen size first is more likely to scale well to QHD than one made for a much smaller screen first).