Google adds 10‑second Pause Point

Google is adding a new friction tool to Android because the old screen-time tricks mostly fail in the exact moment they matter. App timers are easy to dismiss. Full lockouts are too blunt. So Google’s new idea is smaller and more annoying in a deliberate way — a 10-second forced pause before a distracting app opens. Google announced it on May 12 at The Android Show: I/O Edition, and it’s folding the feature into Digital Wellbeing. (blog.google) ### What is Pause Point? Pause Point is a Digital Wellbeing feature for Android that interrupts the launch of apps you’ve already marked as distracting. Instead of opening Instagram, X, YouTube, or whatever your personal time sink is right away, Android makes you wait 10 seconds first. During that gap, the phone asks a blunt question — why are you here? — and offers a few off-ramps, like a breathing exercise, a timer, favorite photos, or a suggestion to open a different app instead. (blog.google) ### Why not just use app timers? Because timers mostly kick in after the behavior has already started. That’s the whole point here. Google is trying to intercept the autopilot moment before the app floods your attention and you forget why you picked up the phone in the first place. The company is pitching Pause Point as a middle ground between “do nothing” and “hard block the app.” That middle ground matters — strict restrictions often get turned off, while soft reminders are easy to ignore. (blog.google) ### Why does 10 seconds matter? Ten seconds sounds trivial, but behavior design turns on tiny bits of friction. The hard part of compulsive scrolling is not that people consciously choose it every time. It’s that they often don’t choose at all. They tap from habit. A forced delay breaks that loop just enough to restore intention. Basically, Google is treating the app launch like a reflex and inserting a speed bump before the reflex completes. That is a much more targeted intervention than a daily usage cap. (blog.google) ### What happens during the pause? This is where the feature gets smarter than a plain countdown. You can use the 10 seconds to set a custom app timer before entering, do a short breathing exercise, scroll through motivating photos, or jump to alternatives like reading, fitness, or audiobook apps. That makes the pause less like punishment and more like a fork in the road. Google is clearly trying to replace one default action with another. (blog.google) ### Can you just turn it off? Not instantly. That’s another intentional choice. Reports from the Android Show say disabling Pause Point requires a phone restart. That sounds minor, but it adds one more layer of friction between “I’m annoyed” and “feature disabled.” In other words, Google is applying the same logic to the escape hatch that it applies to doomscrolling itself. (androidheadlines.com) ### Is this actually new for Google? Yes and no. Google has been pushing Digital Wellbeing for years — dashboards, app timers, Focus mode, Bedtime mode, grayscale, parental controls. But those tools usually either monitor behavior or limit it on a schedule. Pause Point is different because it targets the exact transition into distraction. That makes it feel less like a report card and more like a real-time nudge. (support.google.com) ### Who is this really for? Not everyone. If you open an app on purpose and leave when you’re done, this will just feel like friction for friction’s sake. But for people who unlock their phone, tap a familiar icon, and surface 45 minutes later with no memory of the decision, this is aimed directly at that pattern. Google is not trying to ban distraction. It’s trying to make distraction require one conscious choice. (blog.google) ### Bottom line Pause Point is a small feature with a pretty sharp theory behind it. Google is betting that the best way to reduce doomscrolling is not to shame people after the fact or block them outright, but to slow the first tap. If that works, 10 seconds may end up being more useful than all the screen-time charts Android already gives you. (blog.google)