Development 04 / 04
Maintenance and evolution for software in production
Software is not finished at launch. Dependencies age, operating systems change and users ask for improvements. We keep applications moving – our own and yours.
Use
Where we help
- Updating frameworks, libraries and runtimes.
- Analysing and fixing bugs in existing applications.
- Small and medium extensions based on real feedback.
- Taking over an application whose original developers are no longer available.
Scope
How we work
- Assessment
- With code written by others we start with a review: structure, dependencies, tests, hosting and open risks.
- Priorities
- Security issues and outages first, convenience after that.
- Traceable changes
- Version control, checks before release and short notes on every change.
- Coordination
- An agreed channel for reports and a clear frame for what is included in the support scope.
Practice
From our own products
We build and run our four products ourselves. Updates, bug fixes and further development are part of our daily work – not just the end of a project.
- 01MeineGBUAI drafts for risk assessments, operating instructions and safety briefings.
- 02Verbandbuch.orgThe free digital first-aid log: reports via QR code, access only for authorised roles.
- 03SiGeKoWeb app in beta for health and safety coordination on construction sites.
- 04MyQuickDishQR ordering and digital menus for restaurants, cafés, bars and food trucks.
Framework
What we do not promise
- No blanket response times without an agreed support scope.
- No takeover without first reviewing the code and access.
- No guarantee that every existing application can be developed further economically – sometimes a fresh start is the better choice, and we will tell you so.
FAQ
Frequently asked questions
Do you take over applications from other developers?
Yes, after an assessment. Afterwards you know what state the application is in and which steps we recommend.
Are there fixed maintenance packages?
We agree the frame to suit the application: scope, a channel for reports and how extensions are coordinated.
What do we need to get started?
Access to the code, an overview of hosting and services, and a contact person on your side.
Other focus areas
Next step
Tell us what you are planning.
A few sentences about your goal, users and starting point are enough. We reply by email and suggest a sensible next step.