Why not rewrite your app?

It’s tempting to rewrite the app from scratch, especially now when we know all the features. However, there are risks associated with starting over with a new codebase, even if you have a clear idea of what features and functionality the app should have.

One of the most significant risks is that starting over with a new codebase can lead to a halt in development on the current app. This means that any progress or momentum you have built up with the current app will be lost, and you may need to start from scratch in terms of marketing, user acquisition, and other key areas.

Additionally, starting over with a new codebase can keep you frozen for an extended period of time, potentially delaying the launch of your new app by months or even years. This can be a significant problem if you are operating in a fast-moving market or if your competitors are gaining ground on you.

Finally, starting over with a new codebase can create problems with how the pieces of your app fit together. Even if you have a clear idea of what features and functionality you want to include, there may be other features or components that you need to bolt on afterward, which can be a challenging and time-consuming process.

While there are some success stories of companies like Basecamp that have successfully rewritten their apps from scratch, it’s important to remember that these are often edge cases. For most companies, starting over with a new codebase is a risky proposition that should be approached with caution.

Instead of starting over from scratch, it may be more effective to take an iterative approach to development, continuously refining and improving your existing codebase over time. This can help you avoid some of the risks associated with starting over while still enabling you to build a high-quality app that meets the needs of your users.