Stopwatch in Hand: What Britain's Apps Do With Your First Two Minutes

Two minutes is a decent cup of tea, a queue at a self-checkout, or the amount of time you'll give an app before deciding it's not for you. Multiply that by 124 and you've got over four hours of your life. That seemed like a reasonable thing to measure, so we did.

This isn't a review of features. It's a review of the bit most reviewers skip: the bit before the app does anything, when it's still deciding whether you're allowed in.

How the stopwatch test worked

We took 124 apps that a UK reader might plausibly install this month — travel, banking, shopping, parking, food waste, loyalty cards, council services, a few games — and installed each one fresh. Phone stopwatch, thumb on the start button, ticking from the moment the icon was tapped.

Stop the clock when a genuinely useful task is complete. Not 'the home screen has loaded'. Not 'I have picked five interests from a grid'. Not 'I have agreed to receive updates about my journey'. An actual thing: a forecast on screen, a price visible, a ticket bought, a barcode scannable, a message sent.

Where a task genuinely cannot be done without an account — banking being the obvious example — we logged the account setup separately and then timed the useful bit.

The four walls between you and the point

Almost every slow onboarding we timed came down to the same four obstacles, in roughly this order of damage: the sign-up wall, the permission prompt, the tutorial carousel, and the personalisation quiz.

None of them are evil. All of them are somebody's key metric. Together they turn a thirty-second job into a two-minute ceremony, and two minutes is exactly where a lot of people give up.

Sign-up walls, and the apps that let you look first

The single biggest time sink. An email, a password, a six-digit code that arrives after ninety seconds and reads like it was generated by a rival app. The 'log in with Apple or Google' button shaves maybe twenty seconds off, and yet it's often buried beneath a form.

What struck us is how many apps in the shopping and food-waste categories don't need an account to be useful yet demand one anyway. Browsing prices, checking what's in stock nearby, seeing whether the app is even relevant to your postcode — none of that requires an identity. The apps that figured this out felt a full minute faster than their rivals, and one of them let us get all the way to an order before asking.

Permission prompts before there's any value

Asking for notifications on first launch is the closest thing our stopwatch found to an instant rejection. The prompt lands before you know what the app does, so the only rational answer is 'don't allow'. Location is the same story: fine for a bus app, absurd for a recipe app, and yet the prompt order doesn't always reflect that.

The apps that handled this well asked at the moment of need. Location when you tapped 'near me'. Camera when you tapped 'scan'. Notifications after you'd set one reminder. It costs the developer nothing and it saves the user a small argument with their own phone.

Tutorial bloat and the personalisation quiz

Four swipeable screens explaining that you can save things and search for things is not onboarding, it's a leaflet. We timed one app that took 38 seconds to get through its own introduction, then immediately asked us to pick a minimum of five topics from a grid of 30.

There's a decent rule of thumb here: if a new user has to answer questions before they've seen a single piece of content, the app has put its own segmentation ahead of their time. The best performers skipped the tour, showed the thing, and left a small 'how it works' link for anyone curious.

The ones that respected the clock

A clear pattern emerged. Utility apps with one job were quickest: weather, barcode scanning, translation, torch and measurement tools, a couple of the rail planners. Some had a result on screen in under five seconds.

Marketplace apps that let you browse anonymously came next, usually 20 to 40 seconds to something useful. The strongest of them front-loaded local results rather than a login screen.

Banking and anything involving identity verification took the longest and we're not going to pretend that's unreasonable — the checks exist for a reason. The interesting finding there was variance: two banking apps with similar checks differed by nearly a minute, and it was almost entirely down to how quickly the app told you what it needed and in what order.

Five rules we'd hand to any product team tomorrow

1. Show the thing before you ask for anything. One screen of value changes the mood of every prompt that follows.
2. Ask for permissions at the moment of use, never on launch.
3. Let people browse, compare and search without an account. Save the sign-up for the point where it benefits them.
4. Cut the carousel to one screen or delete it. Nobody has ever finished one and felt informed.
5. If you must collect email, say why in one short line. Vagueness is what makes people lie about their details.

What this means if you're just trying to get on with your day

A rough rule from the stopwatch: if an app hasn't let you do anything useful in about 90 seconds, it's unlikely to become a daily habit. That's not a moral judgement, it's just how attention works when you're standing in the rain waiting for a bus.

And if a sign-up screen appears before you've seen a single price, a single forecast or a single bus time, you're allowed to close it. There's usually a website, and the website is usually less curious about your inbox. The apps that understand this are the ones still on our phones months later — and the ones that don't are exactly why we time them in the first place.