The update that took the feature away

The patch notes are poetry. Performance improvements. Minor bug fixes. A delicate line about how the team has been listening. You update, because you have been asked politely twenty times and the little red dot has started to feel personal, and the app opens looking like itself. Then you try to do the one thing you actually open the app to do, and it is gone.

Not broken. Not relocated. Gone. The feature has been retired, which is a kind word for sent out to sea on a small raft while nobody waves. In its place there is a tidy new flow that solves a problem you did not have, and in the settings, where the useful tick-box used to live, there is a thoughtful essay on why your workflow is now cleaner.

Why this keeps happening

There is a mundane version of this story and a slightly grimmer one. The mundane version is that software teams are small and tired, and anything that has few users and lots of edge cases gets quietly turned off because nobody has the energy to keep it running. That is forgivable. It is also, usually, undocumented, so you learn by stubbing your toe.

The grimmer version is that the feature was removed because it worked too well. It let you export your data without paying. It let you turn off a notification you were supposed to see. It did the job you came for in two taps when the new version prefers you to do it in six, past a banner about an upgrade. Some of these decisions are not accidents. They are a business model dressed up as a redesign.

Either way, you are the one standing in the kitchen at ten past eight with an app that used to work, and the small print of the change-log open on your phone. You do not need a theory. You need the button back.

The disappearing checklist

If you want to be systematic about it, keep a mental list of the things a serious update ought to tell you, and get cross when it does not. Did the release notes mention the thing that was removed? Did they warn you before they pushed the update? Is there a toggle to get it back, even for a few months? Is there a way to export your old data before the new version chews it up?

Most of these questions have the same answer, which is a polite no. This is why trust in the big consumer apps has thinned so visibly: we have learned that an update is sometimes a quiet withdrawal.

Push back, politely

Being grumpy about it in a group chat is a national pastime, but it does not usually bring features back. A short, specific support message often does. Tell them what the feature was called, what you used it for, and what you are going to do instead. If enough people do this, somebody internal uses your words in a meeting, and the feature comes back as a power user option hidden under three menus. That is a win. You will take it.

The Consumer Rights Act 2015 is on your side for software you have paid for: it should be of satisfactory quality and fit for the purpose you were sold on. Which? keeps a readable summary. If the update has turned a paid app into something materially worse, a short, dated note to customer service is reasonable. People do not always refund, but they do sometimes listen.

An update should add. When it quietly subtracts, call it what it is: a withdrawal.

How to keep the old thing working for a little longer

Where you can, turn off automatic updates for the apps you actually depend on. The App Store and Google Play both have per-app toggles for this; your laptop has a similar tucked-away setting. You are not meant to leave them off forever, because security patches matter. You are allowed to delay a release by a week, read the complaints, and then decide.

For web apps, bookmark the old URL. Sometimes a redesign is mounted on a new path, and the old one keeps working for another six months because nobody has had time to delete it. For hardware with software on it, print the manual. Really. Keep it in a drawer, with a pen attached. The useful one is usually under legacy in the firmware section, and the manufacturer is not going to tell you when it goes.

And, once a year, back the thing up. Not the account. Not the sync. The actual file, dragged onto a hard drive you can still read in five years. The great modern trick is to make the update feel like the only copy that ever existed. You can quietly keep a less convenient one.

A fair word for the developers

Not every removal is cynical. Some features were built in a hurry, used by three people, and are a security risk now. Some are gone because the law changed. Some are gone because the company that made the thing was bought, and the new owner is a hedge fund. In most of these cases, a polite note in the release would be enough: we have removed X because of Y, and the nearest thing that still works is Z. That costs nothing. It would help.

The quiet withdrawal

The point is not that software must never change. It is that when a thing you have come to rely on is going to disappear, it is an act of decency to say so clearly, in English, before it does. An update that takes something away without naming it is a nudge dressed as progress, and nudges wear out. You start suspecting the next one. You lose faith. You try harder to use less software. That is probably no bad thing.

Meanwhile, somewhere in a changelog near you, a developer is writing the words streamlined for clarity. Keep your hard drive handy. They do not always mean what you hope they mean.