Web applications

We use React with Next.js for most new applications because it supports server rendering, has strong tooling and is widely known by engineers. We also work with Angular and Vue, and we continue in the framework you already use when that is the sensible choice. The decision depends on your team’s skills, what the application must do and what you will maintain afterwards.

The number of user roles and workflows, the integrations behind the application, the languages and layouts it must support, and its security and audit needs. Design depth matters too: a tool for a small internal team needs less than a public portal your clients rely on. We estimate from the backlog after discovery, so you can decide what goes into the first release.

We design and build to WCAG 2.2 AA. That covers keyboard use, screen readers, colour contrast, focus order, text resizing and clear error messages. Automated checks run on every change, and we test the key journeys by hand with assistive technology before each release. If your organisation follows a stricter standard, we work to that one.

Yes. We keep every piece of text out of the code so it can be translated, and we lay out pages with logical properties so they mirror correctly for right-to-left languages such as Arabic. Dates, numbers and currencies follow each locale. We plan this from the start, because adding a second language to an application built for one is far more work.

We follow the OWASP guidance: input validation, output encoding, protection against cross-site request forgery, secure session handling and a strict content security policy. Permissions are checked on the server, never only in the browser. Dependencies are scanned for known vulnerabilities on every build, and we run security tests before each release. A specialist penetration test can be added before launch.

We agree a performance budget at the start, covering page weight and load time on a typical phone and connection, and check it automatically on every change. Pages render on the server where that helps, images and scripts load only when they are needed, and data is cached close to users. Real-user monitoring after launch shows where the application slows down.

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.

We can run and maintain what we build: monitoring, incident response, security updates, and changes as your business and its partners change. Support is agreed in writing, with response targets, escalation contacts and regular reporting. Our team is available 24/7.