Quick answer
The front end is everything a user sees and touches in the browser: layout, buttons, forms and how fast pages feel. The back end is the server side they never see: the database, logins, business rules, payments and connections to other systems. Most business apps need both, and you should ask your developer specific questions about each.
A builders’ merchant in Stoke wants a portal where trade customers can check prices, reorder materials and download invoices. The first developer talks about “React on the front end and a Node back end”; the second mentions “a Laravel monolith”; the third says they are “full stack”. All three might do a good job, but the owner has no way to compare them, or to know which questions would expose a weak proposal.
You do not need to learn to code to commission software well. You do need to know what the two halves of an application do, where the risks sit in each, and what a good answer sounds like. This guide covers exactly that.
The restaurant analogy
Think of a web application as a restaurant. The front end is the dining room: the décor, the menu, the waiting staff and how pleasant it is to order. The back end is the kitchen and the stockroom: recipes, ingredients, stock levels, hygiene rules and the till that records every sale. Diners only see the dining room, but a bad kitchen ruins the evening however nice the tables look.
Web applications work the same way. Your browser asks a server for a page, the server works out what to send back, and the browser displays it. Mozilla’s guide to how the web works walks through that conversation step by step if you want the technical version.
What lives where
| Front end (in the browser) | Back end (on the server) |
|---|---|
| Page layout, colours, typography | The database that stores customers, orders, jobs |
| Buttons, menus, forms and validation messages | Logins, passwords and permissions |
| How the app behaves on phones and tablets | Business rules: pricing, discounts, approvals |
| Loading speed as the user experiences it | Payments, invoices and emails sent by the system |
| Accessibility for keyboard and screen reader users | Connections to other software through APIs |
| Charts and dashboards drawn on screen | Backups, logs, security and hosting |
Some things span both. A form, for example, checks your input in the browser so you get instant feedback, and then checks it again on the server, because anything sent from a browser can be tampered with. A good developer does both; a weak one trusts the browser.
What “full stack” means
A full-stack developer works on both halves. For small and medium business projects, a full-stack developer or a small team covering both is often the most efficient arrangement, because one person understands the whole flow. Larger projects split the work between front-end and back-end specialists.
Neither is better by default. What matters is that someone owns each half and that they talk to each other. If you are weighing a freelancer against a team, our guide to freelancers versus agencies covers the wider trade-offs.
Why the split matters to you
Understanding the split helps you in three practical ways:
- Reading quotes: a proposal that spends pages on screens and one line on data, security and hosting is front-end heavy. The risky work may be underpriced or missing.
- Spotting the real cost: attractive screens are visible and easy to judge. The back end is where integrations, permissions and edge cases hide, and where most of the time usually goes.
- Planning for later: the front end can be redesigned relatively easily. A poorly designed database or tangled business logic is expensive to fix once real data is in it.

Questions to ask about the front end
- Which devices and browsers will you test on? Look for named phones, tablets and current browsers, not “all of them”.
- How will you make it accessible? A good answer mentions keyboard use, screen readers, colour contrast and form labels. Our guide to website accessibility explains why it matters.
- How fast will key screens load, and how will you measure it? Google’s Core Web Vitals give clear targets, such as the main content appearing within 2.5 seconds.
- Can we see screens before they are built? Wireframes or clickable prototypes cost little and catch misunderstandings early.
- What happens when something goes wrong? Error messages should tell users what to do next, not show a code.
Questions to ask about the back end
- What will the data look like? Ask for a simple description of the main records (customers, jobs, invoices) and how they relate. If they cannot explain it plainly, they may not have thought it through.
- How are logins and permissions handled? Who can see what, how passwords are stored, whether two-step login is available.
- How do you protect against common attacks? A confident developer will refer to the OWASP Top 10, the widely used list of the most critical web application security risks, and explain how they address them.
- Where will it be hosted, and who looks after it? Updates, monitoring and who you call at 7am when it is down.
- How are backups taken and tested? Frequency, where they are kept, and when a restore was last tried.
- Which other systems will it connect to? Accounts, CRM, payments, email. Each integration is a piece of back-end work with its own risks.
- What happens as usage grows? Not every app needs to scale to thousands of users, but you should know where the limits are.
Questions that cover both
- Who owns the code, and where is it kept? You should own it and have access to the repository, not just the live site.
- What documentation will we get? Enough for another developer to take over if needed.
- How are changes tested before they go live? A separate test or staging version is standard practice.
- What does support look like after launch? A defined period of fixes, then a clear maintenance arrangement.
Technology names, decoded
Proposals are full of product names. You do not need to judge them technically, but it helps to know which half each one belongs to:
- HTML, CSS and JavaScript are the basic languages of the front end. Every website uses them.
- React, Vue and Angular are popular JavaScript frameworks for building interactive front ends.
- PHP, Python, Node.js, Ruby, Java and C# are common back-end languages.
- Laravel, Django, Rails and Express are back-end frameworks built on those languages.
- MySQL, PostgreSQL and similar are databases, the back end’s filing system.
- WordPress covers both: it has a back end (the admin area and database) and themes that produce the front end.
The useful question is not “which is best?” but “why did you choose this, and how easy will it be to find another developer who knows it?” Mainstream, well-supported choices protect you if your developer moves on.
A worked example: the merchant’s trade portal
Go back to the builders’ merchant in Stoke. Split into halves, the portal looks like this.
Front end: a login screen, a product search that works on a phone in a van, a basket for reorders, an invoice list with download buttons, and an account page. It needs to be quick on a weak signal and simple enough for customers who will never read instructions.
Back end: customer accounts linked to each firm’s trade pricing, stock levels pulled from the merchant’s existing system, order rules (credit limits, minimum quantities, delivery days), invoices fetched from the accounts package, and a record of who ordered what. It needs secure logins, permissions so staff at one firm cannot see another’s prices, and backups.
Seen that way, the owner can ask sharper questions: how does pricing reach the portal, what happens if the stock system is offline, who can change a credit limit? Those answers tell you far more about a developer than a polished mock-up.
Red flags in a proposal
| What you see | What it might mean |
|---|---|
| Lots of screen designs, little on data or hosting | Back-end work underestimated |
| “We’ll sort security later” | Security not designed in |
| No mention of backups | Data at risk |
| Code hosted only in the developer’s account | You may not control your own software |
| Fixed price with no written scope | Disputes when features turn out larger |
| Unusual or very new technology with no reason given | Harder to find another developer later |
How to write a brief that covers both halves
You do not need technical language. Describe:
- Who uses the app, and what each type of user needs to do.
- The information it stores and where that information comes from today.
- The rules: who can approve, how prices are worked out, what triggers an email.
- Which existing systems it must talk to.
- What success looks like after six months.
The first point shapes the front end; the next three shape the back end. Our guide on how to brief a designer covers the visual side of that brief in more depth, and our comparison of no-code and custom development helps you decide whether you need a custom build at all.
What a web application costs
Cost follows complexity, and most complexity lives in the back end: the number of user types, the rules, the integrations and the data. Our guide to web app development costs breaks down the main drivers. Our Web Applications service starts from £1,999 for custom web apps, dashboards, portals and booking systems, with every project scoped before work starts so you know what is in the front end, the back end and the price. All our prices are on the pricing page.
If you are early in planning, start by listing your users and the three things each must be able to do. Take that list to any developer you are considering and ask them to explain, in plain words, which parts are front-end work, which are back-end work, and where they see the biggest risk. How they answer is often the best guide to who to hire.
Get the UK Website Project Brief Template (free)
A two-page template for briefing any UK web designer: sitemap, integrations, audience and deliverables. Cuts revision rounds in half.
No spam. UK GDPR compliant. We only use your email to send this resource, unless you tick the box to hear from us.
Frequently asked questions
What is the difference between front end and back end? +
The front end is the part of a website or app that runs in the browser: layout, buttons, forms and how it behaves on different devices. The back end runs on the server: the database, logins, business rules, payments and connections to other systems. Users only see the front end, but both have to work well.
What does a full-stack developer do? +
A full-stack developer works on both the front end and the back end. For small and medium business projects, one full-stack developer or a small team covering both is often efficient, because the same people understand the whole flow. Larger projects usually split the work between front-end and back-end specialists.
Which costs more, front end or back end? +
It depends on the project, but in most business applications the back end takes more of the effort. User types, permissions, business rules, integrations and data design all live there. Screens are easier to see and judge, so proposals sometimes underestimate the back end. Ask how the time is split between the two.
What security questions should I ask a developer? +
Ask how logins, passwords and permissions are handled, how they protect against common attacks such as those in the OWASP Top 10, where the app is hosted and who maintains it, and how backups are taken and tested. Ask too who owns the code and where it is stored, so you are never locked out of your own software.
Do I need to understand code to manage a developer? +
No. You need to explain who uses the app, what information it stores, the rules it follows and which systems it connects to. Then ask clear questions about testing, security, hosting, backups and ownership, and expect plain answers. A good developer can explain their choices without jargon.
How much does a custom web application cost? +
Cost follows complexity, especially on the back end: user types, rules, integrations and data. Our Web Applications service starts from £1,999 for custom web apps, dashboards, portals and booking systems, with every project scoped before work begins. Our web app development cost guide explains the main price drivers in more detail.


