Minor Improvements, Major Headache: Six Months Inside 25 UK App Updates

On 12 May 2026, I opened my banking app to send £12 to a friend and spent a full minute looking for the button that had been at the bottom of the screen the night before. The update note had said 'minor improvements and bug fixes'. It had not mentioned that the transfer button now lived somewhere else entirely.

By 6 November, I had a spreadsheet with 25 rows, a folder of screenshots and a mild twitch whenever I saw the words 'What's New'. This is not an anti-update rant. Updates keep apps secure and stop them falling apart. But there is a gap between what a changelog says and what your thumb discovers at 8:15 on a wet Tuesday morning, and that gap is worth measuring.

The Audit: What We Logged and Why

We picked 25 apps that a lot of UK phones carry: banking and payments (Monzo, Starling, Lloyds, Barclays, NatWest), energy (Octopus Energy, British Gas, EDF), travel (Trainline, Citymapper, National Rail), food and coffee (Deliveroo, Just Eat, Greggs, Costa), retail (Tesco, Boots, Argos), media (BBC iPlayer, ITVX, Channel 4, Spotify), public services (DVLA, HMRC, Royal Mail) and parking (RingGo, PayByPhone).

For each one we took a before-and-after screenshot of the home screen, the main settings page and the permissions list. We noted when buttons moved, when defaults changed, when a feature disappeared and when a new permission appeared. Then we scored each app out of five on three things: honesty (did the note match the change?), disruption (how much re-learning did it cause?) and worth (was the change actually an improvement?).

When 'Minor Improvements' Means 'We Moved Everything'

The worst offender in our log was a high-street banking app. The changelog mentioned 'performance enhancements'. On screen, the main transfer button had jumped from the bottom navigation bar to a floating circle near the top right, and the 'pay someone new' option had been folded into a submenu. Disruption: high. Worth: debatable. Honesty: one out of five.

An energy app did something quieter but more annoying. After an update in July, our notification preferences were reset to default. We had previously turned off marketing messages and kept only meter-reading reminders. The update turned everything back on. The changelog said nothing. We only noticed because a meter-reading reminder arrived a day late and a promotional push arrived on a Sunday.

A rail app removed the cheapest-fare badge from the journey results list. It was still there, but buried two taps deeper. The note said 'simplified journey view'. Simplified for whom, exactly?

Permissions, Quietly

Two apps in our sample added new permission requests during the six months. One retail app asked for photo library access 'to improve product search'. One parking app on Android added a physical activity permission, which is a strange thing for a parking app to want. We denied both. Neither app stopped working.

That is the tell, really. If an app still functions when you refuse a permission, the permission was probably not essential. It may be useful, but the update note should say so. 'We now use step data to help you find your car' is a sentence a human can understand. 'Minor improvements' is not.

The Features That Went Missing

Not every loss is dramatic. A supermarket app moved its barcode scanner from the home screen into a menu. A catch-up TV app renamed 'My List' to 'Saved' and moved downloads into a submenu. A coffee app removed the stamp-card view from its home-screen widget, which meant opening the app to check how close you were to a free drink.

None of these are scandals. But they add up to a quiet tax on attention. You learn a layout, you build a habit, and then a version number lands and the habit is broken. The apps that handle this well are the ones that tell you what they have done. It is not complicated. It is just courtesy.

The Ones That Got It Right

Credit where it is due. A couple of apps in our sample wrote update notes that actually described the change. One added clearer disruption alerts on the home screen and said so in plain English. Another added dietary filters to its menu and explained where to find them. A third fixed a long-standing bug with saved addresses and admitted it had been broken.

Those notes took maybe ten minutes to write. They saved us ten minutes of confusion. That is a decent trade.

Scoring the Changelogs

Across the 25 apps, the average honesty score was 2.8 out of five. Disruption averaged 3.1. Worth averaged 2.4. Only six of the 25 update notes described a visible change in any meaningful way. Eleven said 'bug fixes' and did considerably more than that.

The pattern was consistent: the bigger the app, the vaguer the note. Smaller apps and newer services tended to explain themselves. That may be because they are still trying to earn the download. It is a habit the big ones could learn.

A Checklist Before You Tap Update

You cannot stop updates forever, and you probably should not try. But you can make the next one less annoying.

• Screenshot your home screen and your key settings before updating anything important.
• Read the 'What's New' text and check the date. If it says 'bug fixes' and nothing else, expect surprises.
• Note your permissions before and after. If a new one appears, ask whether the app still works without it.
• Turn off automatic updates for critical apps: banking, rail, parking and anything you use before coffee.
• Keep a short note of where things live. It sounds ridiculous until the third button moves in a month.
• Wait 48 hours before updating a travel or payment app you rely on. Let other people find the broken bits first.
• Check accessibility settings after a major update. Font sizes, contrast and screen-reader labels are often the first things to slip.

The Point

Updates are not the enemy. Secrecy is. The phrase 'minor improvements and bug fixes' has become a catch-all for moving the furniture and hoping you blame yourself for not noticing. The best apps in our audit treated the changelog as a place to be honest. The worst treated it as a box to tick.

Next time a version number lands on your phone, take a breath, take a screenshot, and read the small print. If the button has moved, at least you will know it was not you.