Skip to content

Service · Browser applications

Web App Development

Commission a browser application that people sign in to and get work done in: a customer portal, a partner dashboard, a booking tool, a data-heavy internal screen or the web version of your product. We choose the rendering approach, front-end architecture and API design to suit how the app will be used, then build it to be fast, accessible and easy for your team to keep changing.

Rendering strategy chosen per route, not by habit

Accessibility and performance budgets set before build

Typed API contract shared by front end and back end

Deliverables

What a web app development engagement delivers.

01Delivered

Application front end

Screens and components for every authenticated workflow, built with a maintained framework such as React, Next.js or Vue, with a component library your team can extend consistently.

02Delivered

API and domain layer

Endpoints that hold the business rules, validate every request on the server and expose a typed contract, so the front end never becomes the only place a rule is enforced.

03Delivered

Authentication and access control

Sign-in with passwords, magic links, social providers or company single sign-on, sessions handled securely, and role-based permissions checked on the server for every action.

04Delivered

Data-heavy views

Tables, filters, search and exports that remain responsive with large record counts through server-side pagination, sensible caching and background generation of large files.

05Delivered

Release and monitoring setup

Automated builds and tests, preview environments for review, error tracking in the browser and on the server, and real-user performance measurement once the app is live.

Early decisions

Technical decisions we settle early in web app development.

01Decided

Rendering approach per route

Server rendering, static generation and client-side rendering each suit different screens. Public, indexable pages and signed-in dashboards often want different answers within the same application.

02Decided

Where state lives

Server data, form state, URL state and purely local interface state are handled separately. Holding fetched records in a query cache, instead of duplicating them inside an app-wide state container, removes a whole class of stale-data bugs.

03Decided

Browser and device support

We agree which browsers, screen sizes and assistive technologies are supported, which sets the testing matrix and avoids late arguments about an outdated browser on one customer’s laptop.

04Decided

Accessibility level

WCAG 2.2 AA is our usual target, and it is set before design so keyboard use, focus order, contrast and form errors are built in rather than patched afterwards.

05Decided

Performance budget

Limits on JavaScript size, time to interactive content and layout stability are agreed per key screen and checked in the build pipeline so regressions are caught before release.

06Decided

Offline and real-time needs

Most web apps need neither, some need live updates, a few need to work without a connection. Deciding early avoids bolting on sockets or service workers later.

Engagement

How a web app development engagement runs.

  1. 01Phase 1

    Map users, tasks and data

    We list who uses the app, the tasks they complete most often and the data each task reads or changes, then agree the routes, roles and API resources that follow from that.

  2. 02Phase 2

    Set the foundations

    Repository, framework, component library, authentication, API contract, CI pipeline and preview environments are put in place before feature work, so every screen builds on the same base.

  3. 03Phase 3

    Deliver workflows in vertical slices

    Each workflow ships front end, API and tests together into a preview environment where your team reviews it in a real browser rather than a static mock-up.

  4. 04Phase 4

    Harden, release and transfer

    Accessibility and performance audits, cross-browser checks and security review precede release; afterwards we watch real-user metrics and errors, then hand over code and documentation.

Fit

When a custom web application is the right choice.

01Good fit

Users sign in to get work done

The app is a tool rather than a brochure: customers, partners or staff log in to view, create and update records.

02Good fit

Reach matters more than device features

Users are on laptops and desktops as much as phones, and the app does not depend on hardware that only native apps can use well.

03Good fit

Your team will keep developing it

You want a codebase built on mainstream tools, documented and tested, that your developers or a future supplier can extend confidently.

A web app is not a website with a login

Marketing sites are read; web applications are used, often for hours a day. That shifts priorities towards fast interactions after the first load, predictable keyboard behaviour, forms that never lose input, and tables that cope with thousands of rows. We design and engineer for repeated, task-focused use rather than first impressions alone.

Rendering is a per-screen decision

Modern frameworks let one application mix server rendering, static pages and client-side interactivity. Public pages that need search visibility benefit from server or static rendering; signed-in dashboards may be better as client-rendered views fed by an API. Choosing per route keeps public pages quick to index and authenticated screens responsive, without forcing one approach everywhere.

We record those choices in the repository so later developers understand why each route behaves as it does.

The server must stay in charge

It is tempting to put business logic in the browser because it feels faster to build. But anything the browser enforces can be bypassed. We keep validation, permissions and calculations on the server, share types between the API and front end so they cannot drift silently, and let the interface focus on presenting state and collecting input clearly.

Accessibility and performance as budgets

Both are much cheaper to achieve than to retrofit. We set an accessibility target and performance limits before design begins, check them automatically in the pipeline where tools allow, and test manually with keyboard and screen reader on key journeys. Real-user measurements after release show whether people on slower devices and networks get the experience the budgets intended.

Built to be changed

Successful web apps are rarely finished. New workflows, roles and integrations arrive every quarter. A shared component library, clear folder structure by feature, tests around critical journeys and preview environments for every change let your team keep shipping without fear of breaking what already works. That maintainability is a deliverable in its own right, not an afterthought.

FAQ

Questions to resolve before the build.

01What affects the cost of a web application?

The number of distinct workflows and roles, complexity of business rules, integrations with other systems, data volumes, accessibility and browser support commitments, and real-time or offline needs. Design maturity matters too: arriving with tested designs reduces effort compared with starting from a brief.

02How long does a web app take to build, and what changes that?

It depends on how many workflows the first release covers, the readiness of APIs or data you depend on, review turnaround on your side and how much design is already settled. We plan around workflows and confirm the sequence once the task map is agreed.

03What is in the handover package for a web app?

The repository with tests, component library documentation, API schema, infrastructure and pipeline configuration, environment setup instructions, accessibility and performance audit results, and a list of known limitations and suggested next steps.

04Who owns the web app’s code and design?

You do. Code, design files and accounts for hosting, domains and monitoring sit with your organisation. Any npm dependency the app pulls in is recorded, with its licence type, in a file at the repository root.

05How do we decide the web app is ready to release?

Each workflow has acceptance scenarios agreed in advance and demonstrated in a preview environment. Release also requires passing the agreed accessibility checks, performance budgets on key screens and the browser matrix, with no open critical defects.

06What does a web app engagement not cover?

Marketing websites, content writing, native mobile apps and ongoing hosting costs are separate. Changes to third-party systems we integrate with depend on those vendors, and long-term support is arranged separately if you want it.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Web Content Accessibility Guidelines (WCAG) 2.2

    The W3C standard used to set and test accessibility targets for web applications.

  2. 02
    web.dev: Web Vitals

    Google’s guidance on the user-centred performance metrics used for real-user monitoring.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.