Extending and modernising existing software
Your application is in daily use, but new requirements, outdated framework versions or a change of provider hold it back. We take it over, understand it and develop it further step by step, without a speculative rewrite.
Software that runs a business is rarely rewritten in one go. We start with an honest assessment and then improve it in small steps that go live one after another.
Typical starting points
The previous developer is no longer available
We work our way into code, database and operations and document what we find, so knowledge no longer sits with one person.
The framework is outdated
We bring older Angular versions up to date in steps. For AngularJS we first check whether a gradual move or a new build makes more sense.
New features or interfaces are needed
For example creating e-invoices in ZUGFeRD format or reading XRechnung files; we know how from building ZugNow.
Maintenance has been left behind
Updating dependencies, fixing errors, adding logging and monitoring, so problems are noticed before users report them.
Updating Angular and replacing AngularJS
Our own web products are built with current Angular. For existing Angular applications this means:
- Inventory
- Which Angular version, which libraries and which build setup are in use, and which of them block an update.
- Version by version
- Angular is updated one major version at a time, with the official migrations, and every step is covered by tests before the next one.
- AngularJS
- AngularJS is no longer maintained. We first clarify whether a gradual move or a new build makes more sense, and you get the reasons in writing.
How we proceed
Assessment
Code, architecture, tests, deployment and operations: you receive a written assessment with risks and recommendations, as part of the concept.
Step-by-step plan
What comes first, what can wait and what should be replaced. The aim is to keep the software running throughout.
Tests as a safety net
Before behaviour is changed, it is covered by automated tests, so changes do not break what already works.
Further development in milestones
Small changes go live one after another. You see progress at every milestone and have access to the repository.
Frequently asked questions
Do we have to rebuild everything?
Rarely. Most software can be improved step by step while it runs. If a new build really is the better choice, the assessment explains why.
Does the software keep running during the work?
That is the aim: changes go live in small steps instead of one big switch-over.
Which technologies do you take over?
Mainly Angular and TypeScript, C# and .NET, Java with Quarkus, and Flutter. We look at other stacks first and tell you openly whether we are the right choice.
What do you need from us to start?
Access to the source code and, where available, documentation and a description of how the software is run. Everything else we work out in the assessment.
Tell us about your project
Describe what you want to have built, your timeline and your budget range. You get a personal reply from the person who would work on your project.
From the first conversation to the handoverSebastian Streng