Angular apps, built
and kept current
We build Angular apps and bring older ones up to date, one major version at a time, with tests around what your users rely on, so your app stays on a supported Angular version.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When the upgrade keeps moving to next quarter
Many businesses run a large Angular app built some years ago, often by a team that has since moved on. It works, so the upgrade waits for a quieter quarter that never quite arrives. Meanwhile the Angular team brings out a new major version, a release that can change how existing code works, about once a year. The gap to the current one widens, and the version the app runs on leaves support: no fixes after that, security included. The newer Angular features, which can make an app quicker to load and simpler to work on, stay out of reach.
What we build
Angular apps, new or years old, built and kept on a supported version, with tests around what your users rely on.
New Angular apps
Business apps, internal tools and customer portals, written in TypeScript, the language Angular apps use, with one way of working your whole team can follow.
Upgrades, one major version at a time
From the version your app runs on to a supported one, one major version at a time: each update, the move to the next major version, follows the Angular update guide and is tested before the next.
Moves from AngularJS
AngularJS apps rebuilt as Angular apps in stages, with the app in use throughout.
Newer Angular features, a part at a time
Newer ways of writing components, the self-contained parts each screen is built from, taken up a part of the app at a time with the migrations the Angular team provides, and finished by hand where they need it.
Forms with clear checks
Long forms that check each answer as it changes, with the checks Angular forms have built in, and say in plain words what needs fixing.
Quicker first loads
Pages rendered on the server, and parts of a screen loaded only when they’re needed, so there’s less to load at the start.
Tests around what your users rely on
Tests around the flows people use most, such as signing in and sending a form, run on every change before it’s released.
Apps everyone can use
Screens that work with a keyboard and a screen reader, built with the accessibility tools the Angular team looks after, and checked by hand.
Connections to your back end
Your app connected to your APIs and the services behind them, on whatever back end you run, with errors explained in plain words.
- Apps on any stack, or help choosing one:Web & App Development
- Older systems behind the app:Legacy Modernization
- Care once it’s live:Support & Maintenance
- Developers in your own team:Hire Angular Developers
A new major version every year
The Angular team brings out a major version, a release that can change how existing code works, about once a year, with smaller releases between them that don’t. Each major version is usually supported for two years: a year of active support, with regular updates and fixes, then a year of long-term support, with critical fixes and security patches only. After that, it gets no fixes at all.
An app moves forward one major version at a time: the Angular update guide sets out what changes at each step, and the Angular update command makes many of those changes in the code itself. Updating with each major version keeps every step small. Leaving it for years means several steps in a row, each tested before the next.
How many major versions behind is your app?
{{ vrNum }} {{ vrUnit }}
Its support
Active support: regular updates and fixes
Long-term support: critical fixes and security patches only
Long-term support, nearest its end: critical fixes and security patches only
Out of support: no fixes, security included
The way to current
Already current
One update to current
Two updates to current, one at a time
Three updates to current, one at a time
Four updates to current, one at a time
Five updates to current, one at a time
Six or more updates to current, one at a time
One major version at a time, each tested
On AngularJS? The update guide doesn’t cover it. Moving off it is covered below.
{{ vrStatus }}
Moving off AngularJS
AngularJS is what the 1.x versions of Angular are called, and the Angular upgrade guide treats the two as different frameworks. An AngularJS app can’t be brought up to date with the Angular update command, so moving it means rebuilding it as an Angular app. AngularJS support ended on December 31, 2021: it has had no fixes since, security included, while browsers have kept changing around it.
The move doesn’t have to stop the business. The Angular upgrade guide describes running AngularJS and Angular side by side in one app and moving its parts across one by one, until AngularJS can be taken out. We move apps that way, in stages, with the app in use throughout.
Start with a review of your Angular app
The review covers its Angular version and where that version stands in its support, the updates between it and the current version and what each involves, its packages, the ready-made code it builds on, and which of them are still looked after and ready for the next version, its tests and what they cover, the newer Angular features it could take up, how it’s built and released, and its accessibility basics.
On AngularJS? The review includes a plan for the move, in stages. No app yet? The first step is one flow, built and released early, so you can try it before the rest is built.
Either way, you get a written review and a proposal for the first step.
Questions worth asking
Which Angular version should we be on?
The current one, or at least one that’s still supported. Each major version is usually supported for two years, so an app updated with each major version stays supported, and one left further behind leaves support. The count above shows where an app stands at each step behind.
How long does an upgrade take?
It depends on how far behind the app is, how many of its packages need replacing and how well it’s tested. The review sets out each update between your version and the current one, and what each involves, so you can plan them.
Is AngularJS the same as Angular?
No. AngularJS is what the 1.x versions of Angular are called, and the Angular upgrade guide treats the two as different frameworks. An AngularJS app can’t be updated with the Angular update command: it moves across by being rebuilt as an Angular app, in stages, with the app in use throughout.
Do we have to rewrite our app to use the newer Angular features?
No. The Angular team provides migrations that change existing code to the newer ways of writing it, and several can be run on one part of a project at a time. Some changes still need finishing by hand, so we check each part before moving on to the next.
Angular or React?
Both build large web apps. An Angular app gets most of what it needs, such as routing, forms and calls to a server, from one team, on one release schedule. React is a library: it puts components together and leaves routing and loading data to the tools a team chooses. We’ll weigh which fits your team and your app.
React & Next.js DevelopmentCan you take over our existing Angular app?
Yes. We read the code, build and run it, check its Angular version, its packages and its tests, and set out in the review what to do first. You decide where we start.
Our app has no tests. Where do you start?
With the flows your users rely on most, such as signing in and the forms they send each day, before the first update. Those tests then run with every change, so a step that breaks one of them is caught before it’s released.
Can it render on the server, for search and a quicker first load?
Yes. Angular apps can render their pages on the server and then make them interactive in the browser, and parts of a page can wait to load until they’re needed, so there’s less to load at the start. Whether a page should render on the server depends on what it shows and who it’s for, so we decide page by page.
Is it accessible?
It can be, and we check that it is. The Angular accessibility guide covers labeling screens for screen readers, and the Angular team looks after tools for announcing changes to screen readers and for keeping keyboard focus inside a dialog. We test each release with a keyboard and a screen reader.
AccessibilityWho hosts it?
An Angular app can be served beside the back end it calls, wherever suits your business. Hosting and the platform beneath your software are a service of their own.
Cloud, DevOps & SecurityHow do you keep it secure?
Angular apps treat every value as untrusted by default and clean it before it reaches the page, which blocks a common attack, cross-site scripting. We keep that protection in place, never building templates from what people type, as the Angular security guide warns, and keep the app on a supported version with packages that are still looked after. Threat modeling, code review and checks in every build sit around that.
Application SecurityWhat does it cost?
It depends on what the app has to do, how far behind it is, and whether it’s new, being brought up to date or moving off AngularJS. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.
PricingCan we hire Angular developers for our own team?
Yes. Within 48 hours of your request we introduce Angular developers suited to your app, all working in your time zone, and the choice of who joins is yours.
Hire Angular Developers
Angular is maintained by a team at Google. React is a trademark of Meta Platforms, Inc. Webair isn’t affiliated with or endorsed by Google LLC, Meta Platforms, Inc. or the React Foundation.
Let’s build it better
Tell us which Angular version your app runs on, or what you need built, and we’ll suggest where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}