2.4 Maintaining and Evolving

Time: ~30 minutes

What You'll Learn

• How to diagnose and fix bugs without panicking
• When to add features and when to say no
• How to keep your app running reliably with minimal effort
• When to rebuild vs. when to patch
• How to know when your app is "done"

Key Concepts

Your app is live, people use it, and it works. The question now is: how do you keep it that way without it becoming a second job?

Handling Bugs

Bugs will happen. When they do:

1. Write down exactly what happened. "The form did not submit" is not enough. "I filled out all fields on mobile Safari, clicked Send, and nothing happened -- no error message, no loading spinner" is useful.
2. Tell your AI. Paste the exact description. If you can share error messages from the browser console, even better.
3. Test the fix. After your AI provides a fix, test the exact scenario that was broken.
4. Deploy and verify. Push the fix live, then test it again on the live site.

Adding Features Responsibly

Every feature you add is a feature you have to maintain. Before building something new, ask:

• Is anyone actually asking for this, or am I just imagining they want it?
• Can I solve this problem without code? (Sometimes a process change or a note in the UI is enough)
• Will this make the app harder to use for the people who already use it?

If the answer to any of these gives you pause, wait. You can always add it later. You cannot easily take it away.

Maintenance Routine

Once a month, spend 15 minutes:

1. Check your hosting and database usage dashboards
2. Look at any error logs (your hosting platform has these)
3. Test the main workflow (submit a form, check the admin)
4. Update any dependencies if your AI recommends it

That is it. Fifteen minutes a month keeps a simple app running smoothly.

When Is Your App "Done"?

Your app is done when:

• It solves the problem you built it for
• The people who use it can use it without your help
• You have not needed to change anything in a month

"Done" does not mean perfect. It means good enough to stop thinking about. That is a feature, not a failure. You built a tool that works. Now go run your business.

How to Start

Tell your AI:

My app has been live for a while. I want to set up a maintenance routine.
Here's my stack: [your tools]
Here's my hosting: [your platform]

Help me:
1. Find where to check error logs
2. Set up a monthly checklist I can follow in 15 minutes
3. Review my current dependencies for any updates needed

What's Next

You did it. You scoped a problem, chose your tools, built both sides of an app, deployed it, iterated on feedback, and learned to maintain it. You now have a skill most small business owners do not: the ability to build your own tools.

The next time you think "I wish there was an app for that" -- you know what to do.