11/08/2025
Have you ever heard this question: 𝗨𝗜 𝗼𝗿 𝗯𝗮𝗰𝗸𝗲𝗻𝗱 - 𝘄𝗵𝗶𝗰𝗵 𝗰𝗼𝗺𝗲𝘀 𝗳𝗶𝗿𝘀𝘁?
Most people will say UI.
When an idea pops up, we picture screens, wireframes, colors, and flows - it’s easy to start with what we see. So this opinion is very popular in the early stages.
What about later? What do you mean by later?
Um, I mean, let's move on to another question: 𝗪𝗵𝗲𝗻 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝘀𝗼𝗺𝗲𝘁𝗵𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗨𝗜, 𝗱𝗼 𝘆𝗼𝘂 𝘂𝘀𝘂𝗮𝗹𝗹𝘆 𝗱𝗼 𝘁𝗵𝗲 𝗳𝗿𝗼𝗻𝘁-𝗲𝗻𝗱 𝗼𝗿 𝘁𝗵𝗲 𝗯𝗮𝗰𝗸-𝗲𝗻𝗱 𝗳𝗶𝗿𝘀𝘁?
When it comes to actual development, especially in a fast-paced startup environment, the process rarely happens linearly.
Instead, it usually follows a 𝗳𝗲𝗮𝘁𝘂𝗿𝗲-𝗯𝘆-𝗳𝗲𝗮𝘁𝘂𝗿𝗲, 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 approach:
𝟭. 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 - A new feature typically starts with a short working session that includes:
● Business lead (clarifies requirements)
● Designer (creates UI sketches/wireframes)
● Backend developer (assesses API and data needs)
● Frontend developer (reviews feasibility and integration)
𝟮. 𝗨𝗜 𝗮𝗴𝗿𝗲𝗲𝗺𝗲𝗻𝘁 - Once a viable UI is agreed upon, the team agrees on scope and timeline.
𝟯. 𝗣𝗮𝗿𝗮𝗹𝗹𝗲𝗹 𝘄𝗼𝗿𝗸
The designer translates the approved mockup into HTML/CSS (or a usable prototype).
While the backend developer builds the supporting API and necessary data models.
𝟰. 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 - Frontend developer connects the UI to the backend API, ensuring a seamless workflow.
𝟱. 𝗜𝘁𝗲𝗿𝗮𝘁𝗶𝗼𝗻 - Both UI and API often go through multiple iterations before and after launch, based on technical constraints and user feedback.
So, in modern development, it’s less about "frontend or backend first" than about ensuring both are involved from the start and evolve together. That’s how you avoid imbalances, rework, and missed deadlines.
Found this insight useful? Follow us for more.