DEV Community

Cover image for Backend VS Frontend 🤷‍♂️
Belli
Belli

Posted on

Backend VS Frontend 🤷‍♂️

(From a Mobile Engineer perspective)

As a Mobile engineer I have to admit, most of the jobs I had recently envolves way more than just the FrontEnd. BUT (and this is a big "but")—no one wants to use an app that looks unpolished, isn’t responsive, or ignores fundamental UX principles. This may sound like an advertisement for my field, but creating an app/website that is not only beautiful but also intuitive and easy to use is far from simple. Saying "anyone can do it" really oversimplifies the work involved.

Sure, anyone can slap together a basic UI, but what’s the point of having a robust backend if the user experience is frustrating? End users don’t care about your tech stack—they care about how the app feels in their hands. For a product to succeed, both the Frontend and Backend need to work in harmony.
While it’s true that someone with time and dedication can learn backend concepts —since it’s more structured and logical— it’s a misconception to think frontend is just a matter of "throwing things together".

I’m obviously not saying that backend is easy to learn—there are plenty of concepts and different technologies to master—but saying that frontend can be easily done by anyone is equally absurd. UI/UX design demands creativity, empathy, and a keen eye for detail. Without that passion for creation, even with all the knowledge in the world, frontend work can feel like a frustrating, never-ending chore.

If a frontend role requires backend knowledge, it’s because there’s an underlying expectation that the developer is already well-versed in UI/UX. Otherwise, users will not connect with the product, no matter how good the backend is.

Top comments (0)