How to Fix Your App Without Losing What Already Works

A good repair begins with understanding what works, not rewriting everything. The goal is to solve the problem without creating new ones.

What to prepare

The app address, screenshots of the problem, steps to reproduce it, access to source code if you own it, and a list of features that must not change. Never paste passwords into a chat.

Steps

1. Describe the bug and its effect on customers or staff.
2. Reproduce it and capture the expected versus actual result.
3. Identify the current working baseline and available backups.
4. Review dependencies and determine the smallest safe repair.
5. Test the change in an isolated environment before approving release.

What comes next

A defect report, repair plan, verification checklist, and rollback requirements.