Angular development
Build scalable, high-performanceweb applications with Angular development
Angular ships as one opinionated framework with its own router, forms and build tooling, which suits large internal systems with many developers. We build on current Angular and bring older applications forward, including those that have fallen out of support.
What Angular work covers
Often long-lived business software, so maintenance matters as much as the first build.
Business applications
Form-heavy, role-based systems with many screens, where Angular's conventions help a larger team write code that looks the same throughout.
Major-version upgrades
Moving an application forward one major version at a time with Angular's update guide, and replacing third-party libraries that have fallen behind along the way.
Adopting signals and zoneless
Moving components to signals and removing zone.js where it makes sense, in stages, with tests around the behaviour that depended on the old change detection.
Replacing AngularJS
AngularJS and Angular are different frameworks, so this is a rewrite of the front end. We plan it module by module against the behaviour of the running system.
Angular support, as of October 2026
From Angular's release page. Dates you can plan a budget around.
v22 is active
Released on 3 June 2026, active until June 2027 and on long-term support until June 2028. Signal Forms, asynchronous signals and Angular Aria are listed as stable in this release.
v21 and v20 are on LTS
v21 has LTS until June 2027. v20 finishes on 28 November 2026, so a v20 application has weeks left. Versions 2 to 19 are already unsupported.
A slower cadence from now on
From v22, Angular has moved from a major release every six months to one every twelve, which makes upgrades less frequent. They still need budgeting.
Technical points that affect planning
These often surprise teams coming back to Angular after a few years.
Zoneless by default
Since v21, new applications don't include zone.js. Existing code that relied on zone.js to trigger updates, such as setTimeout callbacks that change state, needs checking before you switch.
Toolchain requirements
Angular 22.0 requires TypeScript 6.0 and Node.js 22.22.3, 24.15 or 26 upwards. That means TypeScript 7 isn't an option yet, and an old CI image may have to change first.
AngularJS is long finished
AngularJS support officially ended in January 2022. Any application still on it has run for years with no project fixes, and modern browser and library support won't improve.
When Angular isn't the choice
For a small site or a quick product experiment, Angular's structure can be more than you need. For pages that must rank, plan server rendering from the start.
How an Angular upgrade runs
Library compatibility usually sets the pace more than Angular itself.
Map the versions
We record your Angular version, TypeScript, Node.js and each UI library, and find which release of each supports the next Angular major.
Add tests where they are missing
Critical journeys get end-to-end tests first, because a framework upgrade shows problems in behaviour rather than in compile errors.
Move one major at a time
Each major is a separate reviewable step that runs Angular's migrations, gets tested and could be released by itself.
Modernise afterwards
Signals and zoneless come after the version work is done, so that a failure has one possible cause and not two.
How we engage on Angular
Upgrades can be quoted by the step. New systems are usually longer engagements.
Each major-version step can be priced once the map of versions exists. New business systems run longer, and suit a dedicated Angular developer or team working with your product owner. Hourly work is from $20/h in USD, invoiced in USD, GBP, EUR or INR.
We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. We can pair with your engineers on the harder migrations. For the API layer, see our Node.js and Laravel pages.
Why no Angular systems are listed
Most of our work is delivered under NDA, so many projects cannot be named.
Internal business systems are the kind least likely to be public, so we describe our way of working with Angular and leave out any list of systems. The version map above is a good way to judge how we think.
Questions about Angular
Usually from teams with an existing application.
We are several versions behind. Can we jump straight to v22?
Is AngularJS to Angular an upgrade?
Do we have to rewrite everything in signals?
Angular or React for a new system?
Tell us your Angular version and your UI library
Those two facts show most of the upgrade path. We will come back with the order we would do it in and what we need to see to quote.
We reply within one business day (IST).