When do I start seeing bugs?

As soon as users start using your app after Oopsie’s turned on. It needs real activity to catch real problems. Give it a bit of time, then come back and - boom - your first bug cards should show up.

Can I tell which bugs affect the most users?

Yep. Oopsie shows you user count and bug count right on each card. You can even sort by them, so the biggest headaches float to the top.

Does this work for mobile apps too?

Yes! If you’ve got Zipy set up in your mobile app, Oopsie works just like it does on web - tracking user pain and pointing you to the weird stuff.

What if the bug isn’t always reproducible?

That’s the best part. Oopsie catches bugs as they happen to real users. So even if you can’t make it break again, you still get a replay of when it did break.

User Frustration with Zipy’s Oopsie AI

Overview

Debugging can feel like playing whack-a-mole - crashes here, weird UI issues there, users rage-clicking everywhere.

Zipy Oopsie AI makes that chaos easier to handle. It spots the most important UI and usability problems for you, and gives you AI-powered hints on what to fix first.

This guide is your step-by-step guide on setting up user frustration detection with Oopsie AI for both web and mobile apps. No magic required - just clear steps to catch issues before they turn into big headaches.

Prerequisite

You must have a Zipy account
You must have Zipy installed in your web or mobile application

Step-by-step Instructions

Step 1 - Turn on Oopsie for your project

Log in to Zipy.
Open the Oopsie section.
See the Enable Oopsie button for your project? Click it.

Now, give it some time. Oopsie needs real user activity to record what’s happening in your app.

After a while, come back - you’ll see all those sneaky UI issues that normally slip by. Oopsie makes sure they don’t go unnoticed anymore.

Step 2 - Pick a bug and dig in

In the Oopsie dashboard, you’ll see a bunch of cards - each one is a UI bug your users actually hit.

On every card, Oopsie shows you:

the bug type and some context, along with a screenshot of the UI issue the user got,
the user count (how many people ran into it),
the bug count (how many times it’s happened).

You're sitting on bugs you can't see - Oopsie shows you where to look.

Try for free

‍

You can even sort the list by user count or bug count with the dropdown in the corner - super handy when you’ve got lots of bugs staring at you.

Now, choose the most important one (hint: start with the biggest impact). Hit View Session on the card, and watch exactly how that bug played out for a real user.

Step 3 - Watch the bug in action

When you open a session replay from Oopsie, Zipy drops you right at the exact moment the bug happened. No scrubbing around.

Now play detective:

What did the user do right before the bug?
Did they click “Add to cart” and see “Oops, something went wrong”?
Or worse - did they click “Pay” and get “Cannot process your request”? (That’s money slipping away).

While you're watching, try noticing these things:

What exactly did the user click? ‍

It’s kind of like watching someone walk through a maze and trying to spot the exact moment they go “oops, wrong turn!”

Any signs of trouble before the bug?

Did they pause, go back, click the same thing twice (or ten times)? Little clues like hesitation or rage clicks can tell you a lot.

Is it a one-time oops or does it keep happening?

Check the Oopsie section! You can see how many users hit this bug and whether it's happening a lot or just a weird fluke.

Your mission is to figure out the trigger.

Was it a broken button? A backend timeout? Some missing UI state?

The replay’s kind of magic - you get to actually see what happened instead of poking around and hoping for clues. You don’t have to guess. You can just… watch it break.