"Design is not just what it looks like and feels like. Design is how it works."
— Steve Jobs, Co-founder of Apple
When I started building projects, my process was simple. Open VS code, create a database, build features, then figure out the interface later.
It worked. At least that's what I thought.
The problem came when I wanted to add new features or change existing ones. It happened when I was creating a personal finance tool. I created a simple database, and the backend was solid, but I only thought of the core features, not the full scope. So I kept adding features and complicating my workflow.
That's when I realized I had skipped an important step: planning the experience before writing the code.
Let's talk about UI/UX and why it matters.
What is UI/UX?
UI/UX stands for User Interface and User Experience.
User Experience (UX) focuses on how a product works. It answers questions such as:
What problem are we solving?
What does the user want to achieve?
What steps will they take?
User Interface (UI) focuses on how the product looks. This includes layouts, colors, typography, buttons, and other visual elements.
A simple way to think about it is this:
UX makes up the structure.
UI makes up the appearance.
Both work together to create a product that is useful and easy to use.
Why UI/UX Matters
Many developers jump straight into coding. After all, writing code feels like progress.
The issue is that code is expensive to change once a project grows.
Imagine spending weeks building a feature only to realize users cannot find it or do not understand how it works. Now you have to revisit your database, backend logic, frontend pages, and tests.
A simple wireframe could have exposed that problem in minutes.
Good UI/UX helps you:
Find usability problems before development begins.
Build features users actually need.
Reduce development time.
Create a clear roadmap for the project.
Choose technologies based on requirements instead of assumptions.
The Initial Design Process
When planning a product, there are several stages that help turn an idea into something usable.
1. Discovery and Research
Before designing anything, you need to understand the problem.
Who are the users?
What challenges do they face?
How are competitors solving the same issue?
This stage helps prevent building solutions nobody will use.
2. User Flows
Once you understand the problem, map out how users will interact with the product.
For example, if someone wants to create an account, what happens first?
Open website
Click sign up
Enter details
Verify account
Access dashboard
Seeing the entire journey helps identify unnecessary steps early.
3. Wireframing
A wireframe shows individual screens.
Wireframes focus on structure rather than appearance. They answer questions like:
Where should navigation go?
Where should important information appear?
What actions should be most visible?
Tools like Figma and Miro are commonly used for this stage.
4. Interactive Prototyping
Image from clay.global/blog/ux-guide/prototyping
A prototype shows how those screens creating in wireframing are connected.
Users can click through the design and simulate real interactions before any code is written.
This makes testing ideas much faster and cheaper.
5. Visual Design and Handoff
After validating the structure, visual elements are added.
This includes:
Colors
Typography
Icons
Buttons
Spacing
Why Developers Should Learn UI/UX
You do not need to become a professional designer. But understanding UI/UX makes you a better developer.
I've made projects with excellent code but poor usability. Technically they worked, but users struggled to achieve basic tasks.
Learning design helps you think from the user's perspective rather than the system's perspective.
Some benefits include:
Higher Demand
Companies want products that people enjoy using. Developers who understand users bring additional value to a team.
Less Rework
A few hours spent designing can save days of rewriting code later.
Stronger Portfolio Projects
Employers are often interested in how you think, not just what you build.
Showing research, wireframes, and user flows demonstrates problem-solving ability.
Useful Across Industries
Design thinking applies to technology, business, marketing, and product development.
Easy to Start
You can begin learning UI/UX without writing a single line of code.
Conclusion
I used to think that design is only meant for the designers and front end developers. Now I'm not an expert because I only recently leant this, but I realized that planning before coding saves a lot of time and frustration.
A good design helps you understand the problem, organize your ideas, and create products people can actually use. It also allows one to view the scope of what's possible and what's not.
Before starting your next project, try spending some time on research, user flows, and wireframes first.
You might be surprised by how much simpler your work will be even before writing your first line of code.