Your app on a supported Angular version, step by step, with no downtime for your users.
For companies running Angular or AngularJS apps past end of support, and products that need to last for years.
The problem
Angular upgrades tend to get postponed so the app never has to stop. Meanwhile unsupported versions stop getting fixes, and every skipped version makes each step bigger.
What you get
Your app on a supported version, upgraded one major version at a time and in use between steps.
- One step at a time, each with its own price: you decide when to take the next one.
- AngularJS to modern Angular, part by part, not one big rewrite.
- Support after the upgrade, with written response times.
How it starts
An analysis of the app at a fixed price. At the end you have the upgrade plan: current version and blocking dependencies, the steps to a supported version, what changes at each step and how it is tested, and the price of each step.
After the upgrade
A monthly retainer with hours included and written response times. The hours cover fixes, later version steps and small improvements. The person who upgraded the app maintains it.
Work
- A management platform in production since 2024, which I evolve and maintain within a small team. It replaced the company's Excel spreadsheets and keeps getting new features while in use.
- Angular modernization for a large industrial group: 12 months in a two-person frontend team, with a reusable, re-brandable UI kit.
- Angular versions 6 through 21 handled on apps in production.
- Feature work on a live production system with no regressions. Read the case →
FAQ
What does it cost?
It depends on the size of the app and how old its Angular version is, so I'd rather give you a real price than a range. Write me a couple of lines about your app and I'll reply with the cost of the analysis: fixed, agreed before we start, no extras. Each upgrade step then has its own price, written in the plan.
Does the app have to go offline?
No. Each step ships as a normal release, tested before it reaches production.
Wouldn't a rewrite be better?
Usually not: upgrading in steps keeps the code that works. If a part does need rewriting, the plan says so and why, and the old part runs until the new one has proved itself.
Do you take on apps others wrote?
Yes: the management platform cited in the work section was inherited, then evolved.