For live products · fixed scope

App redesign, without losing the users you have.

Your product works and people use it. Somewhere between the first release and now, the interface stopped matching what the product does, features are hard to find, onboarding leaks, and every new screen makes it worse. That is a redesign, and the risky part is not the design. It is the rollout.

Start your project

Not ready for a call? Send a URL for a free 15-minute audit: we will tell you which of the four depths below your problem is in.

Scope it honestly

Four depths, one of them is yours

Picking a depth by budget instead of by problem is the mistake that costs twice. What each one changes, how long it runs and what it risks is written out in how to redesign an app; here is the short version we use to scope a project.

Visual refresh. Colour, type, spacing, components. The flows stay exactly where people learned them.
UX-flow redesign. Onboarding, the core task, the checkout, reworked around what the data says people actually do.
Structural (IA) redesign. Navigation and hierarchy. The heaviest of the three, because you are moving furniture people have memorised.
Rebuild. Only when patching costs more than replacing. We will say so plainly, and it is usually not this.

What the engagement includes

Standard scope

An audit of the live product against real usage, not a persona document
Measurable goals agreed before anything is designed, so "better" has a number
Information architecture and the core flows, mapped
Prototypes of the priority flows, tested with real users before the visual layer
The visual layer applied as reusable tokens and components, not as screens
A phased rollout plan, so the change reaches users in slices
Engineering-ready handoff: tokens, states, and the specs your developers asked for last time

Published price: $2k-$15k for a UI/UX engagement, typically 4-5 weeks. A full mobile product is $5k-$20k, typically 4-5 weeks. Every range is on the pricing page, the same for every visitor.

The part that actually carries risk

How it ships without a support spike

Nothing ships in one night

A big-bang relaunch is what spikes support tickets. Changes go out in slices, behind flags where your stack allows it, with the high-frequency actions kept where people expect them.

The metric is chosen first

Retention, task completion, support volume, whichever the audit flagged. Chosen before the design starts, measured on a clean before-and-after window, given enough time to pass the novelty bump.

The old patterns get a bridge

Where something genuinely has to move, users get told once, in the product, in one sentence, not discovered on their own at the worst moment.

Proof

A redesign on a live product

The App Redesign case study is this engagement end to end: a live web app with 1,000+ active users at launch, five screens redesigned around how people actually used the product, then the visual layer the original release never had. The write-up walks through the decisions as well as the screens.

Frequently asked

How much does an app redesign cost?

Our published ranges: $2k-$15k for a UI/UX engagement and $5k-$20k for mobile app design, with multi-surface programmes above that. Where a project lands inside the range is driven by screen count, how many states each screen has, and whether you need a reusable system rather than a set of screens.

How long does an app redesign take?

4-5 weeks for a UI/UX engagement; 4-5 weeks when it is a full mobile product. The design is rarely what sets the calendar, the inventory of screens and states is.

Will a redesign cost us users?

It can, if it ships in one night. That is why this engagement plans the rollout as part of the work: slices rather than a relaunch, familiar patterns kept for high-frequency actions, and a metric agreed before the first screen is drawn so you can see what the change actually did.

Do you redesign the whole app or just parts of it?

Whichever the problem needs, and the four depths above are how we scope it. Buying a visual refresh for a retention problem is the most common and most expensive scoping mistake: you spend the money and keep the problem.

Can you work with our existing design system?

Yes, and it is the cheaper path. If a system exists we extend it; if what exists is a tidy Figma file, we say so and price the difference honestly.

Redesigning something people already use?

Thirty minutes, no slides. Bring the product and what is not working; you get a scope and a number, and an honest answer if a redesign is not the fix.