Should You Fix or Rewrite Your App? 4 Key ChecksShould You Fix or Rewrite Your App? 4 Key Checks
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Wahid's avatar
Bashbits logo
pro
• 2h
Thinking about rewriting your app? Check these 4 things first 👇
Do the main features work? If users can already do the main thing, the foundation is usually fine. Fix the bugs around it.
Is the data model sound? Wrong tables and relationships are the hardest thing to patch. This is the strongest reason to rebuild.
Are the problems in a few places, or everywhere? Slow pages and messy files are usually local. Fix those first.
Is the stack still supported? If not, plan a gradual rebuild, not a big-bang rewrite.
The hidden cost: a rewrite rebuilds the parts that already work, too. Login, payments, reports, all of it.
Quick rule: fix if the foundation is sound. Rebuild only when it isn’t.
Have you ever rewritten an app and regretted it, or wished you had? 👇
Shubham's avatar
pro
• 25m
Agree on the data model being the real test. We rebuilt a travel platform off an old Angular and .NET monolith, and the deciding factor was not the code quality, it was that the data lived in MS Access. If the tables are sound, I would patch every time.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started