Why I can't (and don’t want to) work without UX design
“An app should look good and be intuitive to use.” You usually hear statements like this from a UX designer. Makes sense, it’s their profession. The classic “tooting your own horn” principle. Developers, on the other hand, often think: “If the logic works and the integrations run, then my job is done.”
Let’s be honest: in the world of software development, there’s sometimes friction between the designer and the developer. One wants to perfect every pixel, the other wants to make functional impact. But after years of building, I’ve come to a conclusion I never thought I would reach: I don’t want to do another project without a dedicated UX designer.
Proud of your work (or secretly a little ashamed?)
As a developer, you invest a huge amount of time and energy into building an application. You solve complex puzzles and create features that are meant to add value. It’s incredibly frustrating when those features aren’t used or when you constantly get questions from users who don’t understand how things work.
In the past, I’ve been in a situation where I asked for a different assignment simply because I felt a bit ashamed of the application I had built. Technically, it was solid, but the standard Mendix styling fell short of the user’s specific needs. In moments like that, it’s hard to feel truly proud of the work you spend all day on.
In my current project, things are different. The application is technically sound and looks great. I get compliments from users. Of course, some of those compliments are for the UX designer, but we can’t do without each other: they need my technical implementation and I need their design.
The myth: “UX only costs time and money”
A common argument for skipping UX is that it’s an extra expense. That’s true, if you see it as an add-on. But if you see it as an investment, the picture changes completely. What does good design actually deliver?
- Happy users: Everyone benefits from an intuitive app.
- Time savings: Fewer support questions and less time needed for training.
- Higher productivity: A developer who is proud of their product works with more energy and passion.
That last point is often overlooked. Employee satisfaction and pride are directly linked to the quality of the end product. When I’m proud of what I’ve built, I open my laptop with more enthusiasm and have that extra bit of energy to keep improving my app.
The turning point at Squad Apps
The application I’m currently most proud of was co-designed by a UX designer from Squad Apps. The result? The designer is proud, I’m proud and the user is genuinely happy.
My advice to fellow developers: don’t see a design-first approach as a delay, but as a foundation. It doesn’t just elevate your app. It elevates your own job satisfaction too.
No items found.
