Picture this. You publish 200+ watch faces on Google Play. One Tuesday afternoon you push a mass update — a description rewrite or a target SDK bump. You hit submit, walk away, make coffee.

You come back to 200+ notifications in your Play Console.

Welcome to my actual life.

In a sane world, the next 30 seconds go like this: open the bell icon, click Delete all, done. In our world, here’s what actually happens:

1. Click the bell icon. See the wall of identical notifications.
2. Look for a delete button next to each one. There isn’t one anymore. (There used to be. They removed it.)
3. Click a notification. The console navigates you into the app.
4. Open the bell icon again, this time inside the app.
5. Find the delete icon for that notification. Click it.
6. Go back to the app list.
7. Repeat 199 more times.

You can’t even middle-click to open multiple apps in new tabs from the notification dropdown. The notifications aren’t real links. You have to go back to the list, reopen the bell, click the next app, navigate, delete, back, bell, click, navigate, delete.

If you’ve ever ground a 5-minute task into a 45-minute ritual of muscle memory and quiet rage, you know the feeling.

What used to work

The old design had one tiny detail that solved the entire problem: a delete icon next to each notification, in the dropdown itself. You could clear them inline. No navigation. No round trips. You scanned the list, killed the noise, moved on.

It got removed. Whether that was a redesign decision or a side effect of some larger change, I don’t know. The result is the same: a workflow that used to take 30 seconds now takes 2 hours, and only because someone deleted a button.

The fix is one button

I’m not asking for AI. I’m not asking for filters, smart grouping, or notification categories with custom rules. I’m asking for one button:

Delete all.

That’s it. That’s the entire feature request. A textarea worth of frontend code, maybe one backend endpoint that wasn’t there before. Probably half a day of work for an engineer who knows the codebase. Maybe a sprint if you count the design review that absolutely shouldn’t be necessary for a button labelled Delete all.

Why this matters beyond my watch faces

This is the kind of fix that doesn’t show up on any quarterly roadmap. Nobody is going to write a Medium post titled How We Shipped Delete All And Drove Q3 Engagement. There’s no metric for “developer didn’t have to do something tedious 200 times in a row.”

But it’s exactly the kind of thing that defines whether a tool feels respectful or hostile. Tools accumulate friction in places nobody on the product team can see, because nobody on the product team has 200 apps. The people who feel it most are the people whose feedback never makes it back up the chain.

A quick UX win has three properties:

• It’s tiny to build.
• It removes a specific, repeatable, measurable pain.
• It costs nothing to ship — no migration, no breaking change, no design system rewrite.

Delete all notifications hits all three. So does make the notification a real link so I can middle-click it. So would actually useful filters on the app list page. So do about a hundred other one-afternoon fixes that nobody is doing because nobody is watching.

The real lesson

If you’re building a product, find your delete all buttons. Talk to the user with 200 of something. Watch them work. Notice the click they do over and over and over. That click is your roadmap. Not the keynote feature. Not the AI integration. The button that isn’t there yet.

For Play Console: please. Just the one button.