Skip to content

Maintenance

App Maintenance and Support

After launch, software needs fixes, dependency updates and the occasional feature. I also take over codebases when the original developer is gone.

WhatsApp us your ideaContact form

What you can expect

  • A written picture of the current system
  • Fixes you can verify
  • Optional monthly support

A takeover starts with access, a list of broken flows and a short read of the repo. I tell you what is safe to change and what should wait. I do not pretend a legacy system is healthy if it is not.

Maintenance can be a few paid fixes or a monthly block of hours. You still get notes on what changed. Security updates are prioritised over cosmetic work.

Work is remote and worldwide. I reply on WhatsApp, email or a call, usually within a few hours. You own the source code. Nothing ships without a human review of correctness, security and the handover notes.

How AI helps on this engagement

AI tools help read an unfamiliar codebase faster. I still reproduce the bug and review the patch.

Typical deliverables

  • Bug fixes
  • Small features
  • Dependency updates
  • Deploy support

Technologies we use

  • React
  • Flutter
  • Java
  • Python
  • Node.js
  • Nginx

Frequently asked questions

Can you fix a site you did not build?
Yes, after I can run it and see the issue. Share the repo, hosting and a screenshot.
Do you offer a monthly retainer?
Yes. Hours are agreed up front. Unused scope is not invented to fill a quota.
Will you modernise a legacy app?
When it is worth it. Sometimes a targeted fix is smarter than a rewrite.
How fast is a small bug fix?
If I can reproduce it, a small fix is often days, not a new project.
Who owns the changes?
You do. Patches land in your repository.

Related services