Why I Built Solo.Swipe — and Why I Think You Need One Too

By Gül Eda Aydemir, iOS developer and creator of Solo.Swipe · September 2026

Every other space on your phone has been solved. Email has filters. Files have folders. Apps have a library that sorts itself. Notifications have summaries and focus modes. Then there's the camera roll: forty thousand items, no structure, no maintenance tool, and one interface that was designed for picking three photos to text someone — not for making forty thousand decisions.

That gap is the entire reason this app exists. I want to make the case for why it matters more than it sounds like it should, and why I think a photo cleaner belongs on your home screen rather than in the category of apps you download once and forget.

The last unmanaged space on your phone

Think about what actually happens when a camera roll gets big. Not the storage warning — that's the symptom everyone notices. The real cost is quieter.

You stop looking at your own photos. Not consciously; it's just that scrolling back to something from last spring means passing through four thousand items, so you don't. The library flips from being a record of your life to being an archive you can't navigate, which is a strange thing to let happen to the most personal collection you own.

Then there's the low-level dread. Opening Photos to find one specific picture and being met with a wall of near-identical screenshots is a small unpleasant experience you have several times a week. Multiply that across years.

And there's the practical failure: the storage is full at the moment you want to record something, which means the thing you wanted to capture doesn't get captured.

Apple's Photos app is excellent at a great many things. What it does not have is a review mode — a way to be shown one item at a time and make one decision at a time. Selection mode exists for choosing a handful of photos to share or delete. It was never built for going through thousands, and it shows: tap, tap, scroll, lose your place, start again.

Why the swipe, specifically

The interaction is the whole product, so it's worth explaining why I'm convinced it's the right one.

Photo cleanup is a long sequence of binary decisions on visual information. Two properties follow from that, and almost every design choice in Solo.Swipe comes from them.

1. You need to actually see the photo

   A thumbnail grid hides exactly what you need to judge. You can't tell whether a shot is sharp, whether someone blinked, or which of four takes is the good one at grid size. Full-screen, one at a time, is the minimum for a real decision — which is also why it's faster, despite showing fewer photos at once.

2. The decision cost has to be near zero

   At two seconds a photo, a thousand photos is half an hour. At eight seconds it's over two hours, and you stop after fifteen minutes. A swipe is the cheapest possible input — no aiming at a target, no confirming, no leaving the photo. That difference is not cosmetic; it decides whether the session gets finished.

3. It has to have an end

   "Clean your camera roll" has no end, which is why it never starts. So the library is pre-cut into things you can finish: one day, one album, one location, screenshots, videos, the largest files, a random twenty. Finishing something is what makes you come back tomorrow.

4. Cleaning and organizing have to happen together

   Everyone intends to organize later. Nobody does. So swipe up files the photo into an album right there, in the flow, while you're already looking at it — because a second pass through the library is a project that will never be scheduled.

5. It has to be recoverable

   Fast decisions are only reasonable if being wrong is cheap. Nothing is deleted until you confirm, deletion goes through iOS, and everything lands in Recently Deleted for thirty days. You can be decisive precisely because you have a month to change your mind.

Why there's a raccoon

I'll defend this one, because it's the part people assume is decoration.

Utilities fail at recurring tasks. They're built for the one-time fix: scan, progress bar, confirm, done. That model works for a task you do once — but a camera roll refills every week, so a one-time fix buys you a few months and then you're back where you started, now with the added memory of how tedious it was.

Anything you need to do repeatedly has to be tolerable at minimum and enjoyable ideally. So Solo.Swipe treats a messy library as a case file, and Detective Raccoon works it with you. There are streaks, daily goals, a progress ring, small celebrations when you finish a session. None of it is there to be cute — it's there because the thing that makes cleanup fail is not difficulty, it's not coming back.

Why nothing leaves your phone

This one wasn't a product decision so much as a line I wasn't willing to cross.

A camera roll is the most personal thing on a device. It has your family, your home, your documents, your unpublished work, your bad days. Uploading it to a server so that an app can tell you which photos are blurry is an absurd trade, and asking people to trust a stranger's infrastructure with it is worse.

So every bit of analysis in Solo.Swipe runs on your iPhone, through Apple's PhotoKit and Vision frameworks. There is no Solo.Swipe photo server. There's no account, no sign-up, nothing tied to an identity. Your photos are not uploaded, copied off the device, or shared with anyone — details in the privacy policy, including exactly what the free version's ads do and don't receive.

What actually changes

I want to be careful here, because this is where app marketing usually starts lying. Cleaning your camera roll will not fix your life. It's a photo library.

What I do think changes, and what I've built the whole thing around:

• You start looking at your own photos again. When the library is navigable, scrolling back to last summer is a pleasant two minutes instead of an expedition.
• The storage anxiety stops. Not because you did one big purge, but because the thing that caused it has an ongoing routine attached.
• Finding things becomes possible. Filing keepers into albums as you go means "the photo of the receipt from March" is a search, not an excavation.
• One recurring low-grade annoyance leaves your week. That's a small thing. But small recurring annoyances are most of what makes a phone feel heavy.

That's the honest version of the pitch. It's a specific problem, solved properly, in five minutes a day.

Built solo

Solo.Swipe is made by one person. The code, the design, the raccoon, the localizations, the App Store listing, this page. That has obvious downsides — I'm slower than a team, and I can only do one thing at a time.

It also has one real advantage: there's nobody to talk me into the things that make apps worse. No growth team asking for an account wall so we can collect emails. No analytics SDK watching how you use your own photo library. No roadmap pressure to bolt on features that don't belong. The app does one thing, and it can keep doing one thing.

If you use it and something's wrong — a bug, a gesture that feels off, a category that should exist — you can tell me directly at soloswipeapp@gmail.com or @solo.stasera, and it's me reading it.

Read next