Skip to content
Book a free 30-minute call with an engineer

Angular development

A full framework for large, long-lived enterprise apps.

TypeScriptAngular SignalsRxJSNgRxAngular MaterialAngular SSRNxJestCypress

Frontend

Building with Angular

Angular comes with routing, forms, HTTP, dependency injection and testing built in, and it has opinions about how you use them. That's a cost on a small project. On a large app worked on by several teams for years, it means every module looks familiar, which is why banks, insurers and healthcare companies keep choosing it.

New Angular work for us means standalone components, signals and strict TypeScript, with Angular SSR on the pages that need to be indexed. A big share of our Angular work is modernisation: upgrading apps several major versions behind, finishing AngularJS migrations that stalled, and simplifying NgModule and RxJS code that has become hard to follow.

patients.component.tsTypeScript
1@Component({​
2 selector: "app-patients",​
3 standalone: true,​
4 templateUrl: "./patients.component.html",​
5})​
6export class PatientsComponent {​
7 private api = inject(PatientsService);​
8 query = signal("");​
9​
10 patients = toSignal(​
11 toObservable(this.query).pipe(​
12 debounceTime(250),​
13 switchMap((q) => this.api.search(q)),​
14 ),​
15 );​
16}​

The kind of Angular code our team writes every week.

What we build with Angular

  1. 01

    Enterprise web applications

    Modular apps with role-based access, long complex forms and integrations with your back-office systems.

  2. 02

    Angular version upgrades

    One major version at a time, including the move to standalone components, signals and the new control flow syntax.

  3. 03

    AngularJS migration

    Getting AngularJS 1.x apps onto modern Angular (or another framework) module by module.

  4. 04

    Data-heavy dashboards

    Reporting and monitoring screens with virtualised tables, charts and live data streams.

  5. 05

    Micro-frontend architecture

    Splitting a very large app into parts that teams can deploy independently, using Module Federation. Only when the team size justifies it.

  6. 06

    Angular team extension

    Senior Angular engineers who work within your existing architecture and standards.

Why teams pick Angular

01

Consistent across teams

The framework's conventions keep a 30-developer codebase looking like one person wrote it.

02

One source for the basics

Router, forms, HTTP client, testing and i18n come from the Angular team and upgrade together.

03

Predictable releases

A regular release schedule and the ng update tooling make multi-year planning less risky.

04

TypeScript first

Strong typing is the default, so a lot of mistakes never make it to production.

Good fits

  • Enterprise resource and HR portals
  • Banking and insurance dashboards
  • Healthcare admin systems
  • Large multi-team platforms
  • Complex form-driven workflows

Where we use it

Angular questions

Is Angular still a good choice for new projects?

For large applications with several teams and a long life ahead, yes. Signals, standalone components and faster builds have made recent Angular much lighter than its reputation. For a small marketing site or a quick MVP we'd usually pick something smaller.

How hard is it to upgrade an old Angular app?

Mostly it depends on how many versions behind you are and which third-party libraries you use. Abandoned libraries are the usual blocker. We upgrade one version at a time with the Angular CLI update tooling, fix what breaks, replace dead packages and keep the tests passing at every step.

Can you migrate our AngularJS application?

Yes. AngularJS hasn't had security updates since the end of 2021, so it's worth doing. We normally run old and new code side by side and move features across in batches. That way new development doesn't have to stop for months.

Does Angular support server-side rendering?

Yes. Angular SSR with hydration renders pages on the server, which helps SEO and first-load speed. We use it on public pages and often leave the logged-in area client-rendered, because that's simpler to run.

Pairs well with