It's better to do mobile front end before desktop front end when implementing

Heard this offhand from somebody who heard it from someone else but didn't get any elaboration on why.

Anybody else heard something like this before and can explain why?

if we r speaking for the visual part only I always do the desktop 1st, b/c it's easier to hide things than adding new ones...

I found it's easiest to get the desktop working as the back end comes together, then build for smaller screens after that - resizing the browser window to observe all sizes from max width to min width. Workable/good on all widths, mostly smooth change, some breakpoints. I'll have a page working on all screen sizes before I do another one. Having an indication of the window pixel width in your browser, updating as you resize, helps enormously.

coz "responsive design" as an after thought leads to clunky code that very often breaks in weird screen sizes
If it's mobile first, while handling Tab-screens, means expanding to desktop would be way easier

@We3D If you make the mobile version full featured there is no need to add stuff

@ScriptCoded agreed

@We3D but you literally said the opposite?

@ScriptCoded yep, b/c I do not participate in such projects u described, but still can agree that in such cases it might be good to start it mobile first ;] in my projects the desktop version has much more than the mobile view

yes, we practice mobile first in some apps, it's usually easier to make mobile apps fit for desktop screen than the other way around.