Angular Development

We run every Angular there is — including the one you are stuck on.

Angular is our deepest single stack by volume, and unusually we run the full span of it in production right now: the current release on a platform shipped this year, mid-generation builds on two enterprise systems, an older release on a live clinical portal, and a legacy build still serving a retail storefront that earns its keep.

That range is the point. An Angular application a few generations behind is not a broken application — it is a working one that has stopped being upgradeable by the team that has it. Most agencies quote for a rewrite, because a rewrite is the only thing they know how to price. We have carried Angular applications forward a generation at a time for clients who could not afford to stop, which is a different skill and usually a cheaper answer.

What we build with Angular

Version rescue and upgrades

Staged upgrades a generation at a time, with the application deployable and shipping features throughout — not a feature freeze followed by a rewrite nobody signed off.

Multi-tenant branded portals

One codebase serving several separately branded deployments, each with its own configuration, theming and release, rather than a set of forks quietly drifting apart.

Enterprise admin consoles

Angular Material and CDK back-office applications with role-based access, audit trails and the information density real operators actually want.

Clinical and regulated portals

Patient and practitioner portals with JWT handling, inactivity timeouts, strict template checking and accessibility held to standard.

Analytics and network visualisation

Highcharts and Chart.js dashboards, plus force-directed organisational network analysis over live data using sigma.js and graphology.

Rich authoring and scheduling

Quill and markdown editors with in-browser image cropping, and FullCalendar booking surfaces — so editors and schedulers work inside the product.

What is actually in our Angular projects

Not a wish list. Every library below is running in a repository we maintain.

Core

  • Angular
  • Angular CLI
  • TypeScript (strict templates)
  • RxJS

UI

  • Angular Material
  • Angular CDK
  • Tailwind CSS
  • SCSS
  • ng-bootstrap
  • FullCalendar
  • Swiper

Visualisation

  • Highcharts
  • Chart.js / ng2-charts
  • sigma.js
  • graphology
  • Angular Datatables

Content & docs

  • ngx-quill
  • ngx-markdown
  • ngx-image-cropper
  • ngx-mask
  • jsPDF
  • html2canvas

Auth & integration

  • @auth0/angular-jwt
  • ng-idle
  • OpenAPI Generator
  • Luxon
  • Google Places

Testing & delivery

  • Karma
  • Jasmine
  • Playwright
  • GitHub Actions
  • Azure Static Web Apps
  • Bugsnag

How we work in Angular

Choosing the stack is the easy part. These are the decisions that determine whether the codebase is still maintainable after we hand it over — and they are the same on every Angular project we run.

Our certifications
  • Upgrades run a generation at a time with the application deployable at every step, so the client keeps shipping features while the migration happens underneath them.

  • Strict templates and strict injection parameters are on, which turns a whole class of Angular runtime failure into a build error before anyone sees it.

  • The API client is generated from the backend's Swagger document rather than maintained by hand — the single biggest source of drift in a long-lived Angular application.

  • Karma and Jasmine suites run in CI across every environment branch, so a change is verified against each deployment target rather than only against the main line.

  • Bugsnag reporting spans the Angular client and its .NET backend, so a failed request is one trace rather than two teams comparing timestamps.

Looking for the service rather than the stack?

Angular is how we build. If you would rather start from what you need delivered, our bespoke software development page covers scope, process and engagement.

Bespoke Software Development

Building on Angular?

Tell us what you are building — or what you have inherited. We will come back with a straight answer on scope and approach.

Get in Touch