Why Your Favorite Apps Keep Changing

TL;DR: Apps keep changing because teams test new layouts on small groups of people before everyone gets them, and because they're chasing numbers like how many people finish a purchase. The change that annoys you is often a fix for a problem you never saw. You can turn some of it off, and your complaints do get counted.

You've had the same app on your phone for two years. You know exactly where the search bar sits, where your saved items live, where to tap to pay. Then a Tuesday update moves all three. Nobody asked your permission.

That's not a company messing with you for fun. It's usually one project, with a start date and a deadline, that ended with your screen looking different.

A real project: the tab Instagram added, then removed

In 2020, Instagram put a Shop tab in the main bar at the bottom of the app. Shopping was going to be huge. Two years later the company was still testing ways to make shopping more prominent, and in January 2023 the tab was gone.

That's a full loop: an app redesign, a hard push, then a quiet reversal. Somebody's project got cancelled. Somebody else's replaced it. Most of this never makes the news. Teams ship small layout changes, watch what happens, and undo what doesn't work.

How a redesign gets approved (A/B testing, in plain words)

Most apps can show two versions of the same screen to two groups at once. It's called an A/B test: group A gets the old screen, group B gets the new one.

The team picks a number to watch. Not "does it look nicer" — something countable, like how many people finish a purchase or come back tomorrow. If the new screen wins by enough, everyone gets it. If it loses, it gets deleted.

Here's the catch. "Wins" can mean a tiny difference. Say 21 out of 100 people finish checkout instead of 20. That one extra person can pay for the whole project, so the change ships — even though 79 people still don't finish. The team sees the win. You see a moved button.

Why apps keep changing even when you liked the old version

A few reasons, and only some are about money.

• Muscle memory isn't measured. You built a habit over two years. A test that runs for two weeks can't see that.
• Apps get rebuilt in pieces. Engineers rewrite the code behind a screen, and the rebuilt version rarely looks identical. Same features, new coat of paint.
• Phones change underneath. New screen sizes, new iOS and Android versions, new accessibility settings. Some redesigns exist because the old layout breaks.
• New people want to leave a mark. A designer who joins in March will propose something by June. That's the job.

(My honest read: the resets that hurt most are the ones where a familiar thing moves for no clear payoff. Those often get walked back, but it takes a year.)

What this means for you

• Wait a week before updating. Auto-updates are optional. You keep the layout you know a little longer and skip the buggy first version.
• Hunt for the switch. Settings > Display, or "Classic view", or "Compact mode". Plenty of big apps still hide the old look in there.
• Give it two weeks, not two minutes. Most redesigns feel wrong on day one and normal by day fourteen. If it's still bad after that, it's a real problem.
• Complain specifically. "I can't find my saved items" gets read by a human. "This update sucks" gets counted and ignored.

Key Takeaways

• Apps change because teams run A/B tests and ship whatever wins, even by a hair.
• Big redesigns are single projects with owners, which is why they can also be cancelled.
• Muscle memory costs nothing on a spreadsheet, so it's the last thing teams protect.
• Delay your updates, look for a classic-view setting, and name the exact task that broke.

Frequently Asked Questions