Britain's Cheapest Bug Hunt: Thirty Apps, One Clock Change and the Fortnight That Followed

There is a particular kind of British optimism that assumes the clock change will simply sort itself out. The phone updates, the oven doesn't, and by Tuesday everyone has stopped arguing about the car radio. This year we decided to treat the 25 October switch as something more useful: a free regression test. Thirty everyday UK apps, two phones, one tablet, and a fortnight of slightly obsessive note-taking. The results were less dramatic than a data breach and more annoying than a sodden commute.

Why bother testing something the operating system handles

Most apps don't really 'handle' time. They inherit it, display it, and quietly hope for the best. When the UK fell back to GMT at 02:00 on Sunday 25 October 2026, the devices did the heavy lifting. What interested us was the layer above: the recurring alarm set for 07:15, the gym class booked for 18:30, the pharmacy reminder, the parking session ending at 16:40, the delivery slot labelled 'by 20:00'. Those are the places where an hour either goes missing or turns up twice.

Our method was deliberately unglamorous. We set up alarms, calendar events, medication reminders, fitness goals, train searches, parking sessions and delivery slots before the change. Then we watched what happened between 25 October and 7 November. We used an iPhone on iOS 26 and a mid-range Android handset, both with automatic time and time zone switched on, plus a tablet left on manual time as a control. We checked labels as well as behaviour: a timestamp that says BST when it is already GMT is a small lie, but it is a lie that ends up in a screenshot at work.

The alarms mostly behaved — until they didn't

The built-in clocks on both phones were fine. Apple's Clock and Google's Clock app fired when they said they would, which is the bare minimum and still worth saying out loud. The trouble started with third-party alarm apps that promise 'smart' wake-ups — the ones that watch your sleep and pick a gentle moment in a half-hour window. One of them, a sleep-cycle app with a monthly subscription, woke us at 06:20 instead of 07:00 on the Monday. It had done the maths in the old time zone. Another habit-tracking alarm simply didn't go off at all, then sent a notification at 08:03 saying 'rise and shine'. Not ideal on a school morning.

Calendars, invites and the phantom 09:00

Google Calendar and Outlook handled the switch without a murmur. The problems were at the edges. A leisure centre booking confirmation produced a calendar file that landed at 09:00 GMT but displayed as 09:00 BST in one mail app — same number, different label, entirely different hour. A gym chain's app showed a 18:30 class correctly in the list view but pushed a reminder at 17:30 local time. And a recurring 'team stand-up' that a colleague had set up in a third-party scheduling tool shifted by an hour for everyone except the person who created it. Nobody noticed until the second week.

Streaks, reminders and the extra hour nobody counted

Fitness apps that work in UTC — Strava, for instance, and Apple's own activity rings — sailed through. Two habit apps did not. Both counted the repeated 01:00–02:00 window as a fresh day, which meant anyone who logged a walk or a glass of water in that hour either got a bonus day or, more commonly, had a streak broken for no reason they could see. Medication reminders were the more serious version of the same bug. A high-street pharmacy app fired a daily reminder at 07:00 BST on the Monday, which is 06:00 GMT. An hour early is not catastrophic for a vitamin, but it is not a great look for a blood-pressure tablet.

Trains, parking and the delivery slot that said 19:00

National Rail and Trainline both displayed departures correctly, and the operator app we tested had fixed a labelling issue we'd seen in previous years. Parking was messier. Two of the three parking apps we used showed session end times in BST for several days after the change; the countdown timer was right, the label was wrong. Delivery slots were the most visible failure. One supermarket app insisted a 19:00–20:00 slot was '19:00–20:00 BST' on 28 October, a full three days after BST had left the building. The driver arrived at 19:10 GMT. The app, apparently, was still on holiday.

The label problem is the real problem

Almost every failure we logged came down to labelling rather than arithmetic. The countdown was right; the words next to it were wrong. That matters more than it sounds. A timestamp is a small contract with the reader, and when a UK app says BST in November it is quietly telling you not to trust the rest of the screen. We counted eleven apps still using the wrong label at least once during the fortnight. Only four of them corrected themselves after a force-quit and a re-launch.

The handful that didn't blink

The built-in clocks on both phones, Google Calendar, Outlook, National Rail, Strava and Monzo all handled the switch without a word, which is exactly what you want. Citymapper also got it right, including the bus times. None of them sent a notification to say 'we've updated our clocks'. That is the correct behaviour. The apps that made a fuss about the change were, without exception, the ones that got something wrong.

Your pre-March checklist

The clocks go forward again on 29 March 2026 — sorry, 2027 — and the same bugs will be waiting. Before then, do a five-minute audit:

• Check every recurring alarm, especially the third-party ones with 'smart' windows. Set a test alarm for the morning after the change.
• Re-save medication reminders rather than assuming they'll adjust. A reminder that fires an hour early is easy to miss and hard to explain.
• Open your calendar app and check that 'time zone support' is on and set to London. If you travel, check the events that cross the change.
• Screenshot parking sessions and delivery slots. If the label says BST in November, complain — politely, and with the screenshot.
• Confirm your phone is set to 'Set automatically' for date and time. The tablet on manual time was the only device that got everything wrong, and it got it wrong consistently.
• Check smart plugs, heating schedules and any appliance app that thinks it knows better than the thermostat.

The hour going backwards is the cheapest stress test your phone will ever run. Most of the thirty apps we tested passed. A handful failed in small, quiet, entirely predictable ways. The difference between a good app and a merely adequate one is whether anyone notices at all.