← All posts

Studio

Does Anyone Else Have This Problem? Validating Hidden Pain Points

17 Jul 20267 min readStudio

Some problems are loud. Your app crashes, your flight is delayed, your bill is wrong — you complain, someone else complains with you, and you know immediately that it's not just you.

Then there are the quiet ones. The ones that annoy you for thirty seconds and then you move on. You never mention them to anyone, because who would you even mention them to? It's not a complaint. It's barely a thing.

This is a post about one of those.

The thirty seconds that turned into ten minutes

I was looking for a bill. I knew I had screenshotted it. I could almost picture it — roughly when, roughly what it looked like.

So I opened my gallery and started scrolling.

Somewhere around minute four, the scrolling stopped being about the bill. My head went somewhere else entirely. Where do I get this bill if I've actually lost it? Who do I call? Did I even take the screenshot, or do I just think I did? That last one is the worst, because now you're not searching a folder, you're interrogating your own memory.

I found it. It took a while, but I found it.

And then I did the thing that everyone does. I starred it.

There's a small, satisfying lie in starring something. You feel like you've fixed the problem. You haven't. You've just made a note to your future self that this one particular screenshot mattered, on the day you happened to need it.

Because a few days later, same thing. Different screenshot, same scroll, same spiral. I starred that one too.

That's when it stopped being a bad day and started being a pattern. This was going to keep happening. Not maybe — definitely.

So I looked at my gallery properly for the first time. 578 screenshots.

And the obvious question: do I star all of them? Even if I only star the useful half, that's 250 starred screenshots. Which is just my original problem, wearing a slightly nicer shirt. I'd be scrolling through a smaller pile with more confidence and the same outcome.

Starring wasn't the answer. What I actually wanted was for the pile to have shapes in it. Bills here. Books there. Places. Recipes. Not one enormous folder with a few gold stars scattered across it.

That's where Upshot started. Not with a market, not with a plan. With a bill I couldn't find and the realisation that no phone I've ever owned has offered me anything better than a star.

The part where I should have asked first

I'll be honest about the order I did things in, because it's not the order the books recommend.

I built it first.

I made the sorting feel like a game instead of a chore — swipe right to file it, swipe left to bin it, deal with the bin later in one go. Something you could do in a queue without thinking about it. That part I enjoyed. That part was easy.

Then I finished, looked at the thing on my phone, and had the thought I probably should have had four weeks earlier:

Is this just me?

And immediately behind it, three more:

How would I even validate this? Who do I ask? Should I ask at all — or will I just look like someone who's made a big deal out of nothing?

That last question is the one that keeps quiet problems quiet. Nobody wants to walk up to a colleague and say "hey, do you also find it mildly annoying to locate old screenshots?" It sounds like nothing. It sounds like you've built an app for a feeling.

I asked anyway.

The lipstick

I asked a colleague. Deliberately, I said nothing about the app — I just asked whether she ever had trouble finding old screenshots.

She didn't say "yeah, sometimes." She told me a story, immediately, like it had been sitting there waiting for someone to ask.

She'd been staying at a hotel. She'd lost a lipstick — one she'd searched a long time for, the one that actually worked with her skin tone. Gone. But she knew, with total certainty, that she had a picture of it. A screenshot, somewhere, in a gallery with thousands of images in it. And she went looking. For a long time.

I want to be clear about why this mattered to me. It wasn't that she agreed with me. It's that she had a completely different life. No bills, no warranty cards, nothing that overlapped with my version of the problem at all. A lipstick in a hotel room.

Same panic. Same scroll. Same interrogation of her own memory.

If she'd said "yes, I have that problem too," I'd have wondered how much of that was politeness. She didn't say yes. She just started telling me about the lipstick. You can't be polite in that much detail.

That was the moment the thing stopped being mine.

The lawyer

The second conversation I didn't ask for at all.

I'd shared the app with a friend, casually, the way you do. A week later we met and he brought it up on his own.

He'd needed to send a set of screenshots to a lawyer. Before, that meant going into the gallery, hunting for each one, long-pressing, selecting, hoping he hadn't missed any, and sending a pile of loose images. With Upshot, the screenshots were already in a folder — so he selected the folder and sent it across as a single PDF.

Now: I did build that feature. I know it's in there. But I built it as a tidy little convenience — nice to have, sits in the menu, fine.

He was using it as the whole point. To him the app wasn't a screenshot organizer. It was the thing that made a slightly humiliating task not humiliating.

The first conversation told me the problem was real. The second told me something harder to hear and better to know: the thing you build stops being yours the moment someone else picks it up. They'll find the use you didn't design for and treat it like the main event. Your job is to notice, not to correct them.

What I actually learned

Not much of a framework, but here's what I've got.

The quiet problems are the ones worth checking. Loud problems already have ten apps solving them. Quiet ones have nothing, because nobody complains loudly enough for anyone to notice — including you.

Don't ask "do you have this problem?" You'll get politeness. Ask about the situation and shut up. If it's real, you won't get a yes — you'll get a story, unprompted, with details nobody would bother inventing. Like a lipstick.

Ask, even if you built it backwards. I did it in the wrong order and it worked out. It could just as easily not have. But the version where I never ask, and never find out, and just quietly assume — that one's worse than being wrong.

Someone will use it in a way you didn't plan. That's not a bug. That's the first sign it's actually theirs now.


Upshot organises your screenshots by swiping — right to sort into folders, left to bin. Everything runs on your device, and you can search inside your screenshots offline using OCR.

Try Upshot on Google Play.

If you want the backstory, read why we built Upshot. If you want to know how it works under the hood, read how to find screenshots easily.