Tithi Mondal

Article6 min readUpdated

App Redesign or Rebuild: How to Decide and Roll Out

App redesign or full rebuild? Learn how to decide, what a redesign includes, and how to roll out changes without losing the users you already have.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

App Redesign or Rebuild: How to Decide and Roll Out: cover illustration

Imagine a coaching centre with 300 students. Two years ago, the owner paid for an app. Students use it to see class timings and download notes. Now the owner gets calls every week: "Where is the test result?" "How do I pay the fee?" The owner asks one question: "Should I throw this app away and build a new one?"

Usually the answer is no. Most of the time, the owner needs an app redesign, not a rebuild. This article explains how to tell the difference, what a redesign includes, and how to change an app without losing the users you already have.

Redesign and rebuild are different jobs

A redesign changes what users see and do: screens, layout, flow, words, colours. The code behind it may stay mostly the same, or change only where needed.

A rebuild replaces the code and technology itself. The developer starts again from the base. Often a rebuild also needs a redesign, but a redesign does not always need a rebuild.

Think of a shop. A redesign moves the shelves, improves the signboard and puts the billing counter near the door. A rebuild demolishes the shop and builds it again. Sometimes demolition is right. Usually shelves are the problem.

Signs you need a redesign

These problems live in design, not in code.

  • Users cannot find a main feature. The fee payment is hidden under a menu called "More".
  • Many people open the app but stop at the same screen.
  • Support messages ask the same question again and again.
  • The app looks old next to apps your users use daily.
  • New features were added one by one, and now the screens feel crowded.
  • The app works badly in Bengali, Hindi or another language your users read.

If your list looks like this, start with a redesign. A UX audit is a good first step. It finds the real problems before anyone changes a screen.

Signs you may need a rebuild

These problems live in the technology. A designer cannot fix them with better screens.

  • The app is very slow or crashes even on good phones, and developers say the base is the cause.
  • The code is so tangled that every small change breaks something else.
  • The technology is outdated and cannot be updated for new phone versions.
  • The app must work on a platform it does not support now, for example you have only Android and need iPhone too.
  • No developer wants to work on it, and the original developer is gone with no notes.

Ask your developer for a plain written reason. "It feels messy" is not a reason. "The payment module cannot be updated without rewriting the login" is a reason. Where I am unsure about code, I say so, and I ask the developer to explain it in simple words.

A fast way to decide

Answer these three questions in order.

  1. What exactly do users complain about? Write the top 5 complaints from calls, WhatsApp messages and app store reviews.
  2. Would a better screen fix each complaint? If yes, it is a design problem.
  3. Does the developer say the code blocks the fix? If yes, that part may need new code.

Most founders find that 4 of 5 complaints are design problems. That is why I suggest a redesign first, then a rebuild of only the parts that truly need it. Rebuilding everything is the most expensive path, and it is the one with the longest wait before users see any benefit.

What a redesign includes

A redesign is more than a new coat of paint. Here is what I look at, in the order I do it.

  1. Understand. I study how people use the current app. I read reviews and support messages, and I talk to a few real users, if possible.
  2. Map the flow. I draw the main journeys, such as "pay a fee" or "see a test result", and count the taps each one takes.
  3. Wireframe. I rearrange screens in plain boxes before any colour appears.
  4. Design the interface. I update layout, type, colours, icons and words. This is often called a UI refresh.
  5. Prototype and hand off. I build a clickable version for testing, then give the developer organised files.

A UI refresh alone, which means only colours and icons, is the cheapest option. It helps when the app looks old but works well. It does not help if users get lost, because the flow stays the same. Be clear with your designer about which one you want. For a deeper look at stages, read about the mobile app design process.

A redesign can also build a small design system, which is a shared set of buttons, colours and text styles. This keeps fifty screens consistent. See design system for startups.

How to roll out a redesign without losing users

Users do not like surprises. A person who has paid fees in your app every month will be upset if the Pay button moves overnight. Here is a safer way.

Keep the anchors in place

Choose 3 to 5 things users do most often. Keep these actions easy to find, in or near the same place. Change the look around them first.

Release in stages

Do not change everything on one day. Release the most helpful change first, for example a simpler fee payment screen. Then release the next. Developers call this a staged release.

Test with a small group

Before the full release, give the new version to 10 to 20 existing users, such as a few students and parents. Watch where they hesitate. Then fix those places.

Tell users in plain words

Put a short note on the first screen: "We made paying fees easier. Your old receipts are still here." Do not use long release notes. Send the same message on WhatsApp if that is how you reach users.

Keep an old route for a short time

If a main flow changed a lot, keep a "How do I...?" help link or a WhatsApp number. Remove it only when support messages drop.

Watch the first two weeks

After release, read every complaint. Some will be habit and will pass. Some will show a real mistake. Learn to tell them apart.

Cost, time and honesty

A redesign costs less than a rebuild in most cases, but price depends on the number of screens, user roles and depth of research. I give a custom quote for app design, because two apps with the same number of screens can need very different work. You can see what drives cost in mobile app design cost in India and try the cost calculator.

A redesign will not fix a product nobody needs. If users do not want the core service, new screens will not change that. A designer should say this honestly, and I would rather tell you that early than sell you screens.

If your own app has problems and you are not sure whether they are design or code, I can review it with you through UI/UX design, or you can write to me here.

Frequently asked questions

Is an app redesign cheaper than a rebuild?

Often yes, because a redesign changes screens and flows while keeping working code. The exact cost depends on the number of screens, user roles and the research needed.

How long does an app redesign take?

A redesign usually takes a similar time to a new app design, since the screens still need mapping, wireframes and testing. Development time after that depends on how much code changes.

Will users leave if I change the app design?

They may, if main actions move without warning. Keep the most-used actions in familiar places, release in stages and tell users what changed in plain words.

What is a UI refresh?

A UI refresh updates the look of an app, such as colours, icons and type, without changing how it works. It suits apps that function well but look old.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.