IT Glossary
What is a Frontend?
The visible part of an application: everything that displays and reacts in the user's browser or on their phone.
Everything a user sees, taps and waits for on your site or app is frontend: the pages, buttons, forms, animations and error messages — code running in the visitor's browser (HTML, CSS, JavaScript and their frameworks: React, Vue, Angular), in dialogue with the backend, the unseen engine on the server. The split is economic as well as technical, and worth understanding when reading quotes: “we'll redo the design” is frontend work (the engine stays), “we'll add installment payments” is mostly backend with a frontend face, and “the app is slow” could be either — diagnosis comes before the estimate. For the business, the frontend carries a disproportionate responsibility: it is where first impressions and conversions happen — where a visitor decides within seconds whether to stay, where one extra second of loading or one confusing form measurably cuts sales, where mobile adaptation (the majority of traffic) and accessibility play out. The classic evaluation trap: a beautiful frontend shows at the demo; a good frontend shows in use — fast on a mediocre phone with weak signal, clear when errors happen, usable without instructions. Demand the second; the first comes anyway.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
First impressions under control
A polished, fast interface signals competence instantly — clients judge the company by the only part of the software they ever see.
Conversions defended technically
Clear forms, quick loading, flawless behavior on phones — frontend details that count directly in submitted orders.
A facelift without demolition
With a proper frontend-backend separation, a redesign never touches the engine — the storefront is renewed at storefront prices, not building prices.
Frequently asked questions
A developer is “frontend only” — does that mean they can't do everything?
It's a specialization, as with physicians: the frontend demands mastery of interfaces (languages, frameworks, device adaptation, accessibility), the backend of servers and data. “Full-stack” covers both at varying depths. On serious projects, the mixed team is the norm, not the exception.
Why do “just a few interface tweaks” take weeks?
Because a correct interface is multiplication, not addition: each screen × devices (phone, tablet, desktop) × browsers × states (empty, full, error, loading) × accessibility. The “simple” button lives in dozens of contexts — and the untreated ones are exactly where customers stumble.
What is server-side rendering, and why do proposals mention it?
It's about where the page gets baked: on the server (SSR — the page arrives ready-made: fast display, friendly to Google) or in the browser (SPA — fluid in use, but harder to index without extra care). Modern frameworks like Next.js combine the two. For you: public sites that must be found need SSR or an equivalent; internal applications live comfortably without it.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247