Oploads AI

The situation

Teams were losing files. It wasn’t in the “someone deleted the folder” way. It was the slow, exhausting way, where files live across paper, email threads, three different cloud tools, and someone’s desktop. A request goes out. The file goes missing. Someone follows up. Someone else follows up. The work stalls.

You know that feeling. Everyone does.

The founder wanted to fix it. Oploads was going to be the calm center of file management for teams, especially the ones still fighting with paper and digital at the same time.

What I did

Full product experience. Landing page, design system, the web application interface, mobile responsive states. I set the visual language and interaction patterns from scratch, and shaped how the AI layer (still on the roadmap when I designed it) would eventually fit in without breaking the calm.

How I approached it

Calm was the whole product.

Every screen had to answer one question fast: “where is my file?” I designed around that question first. Everything else came after. If a screen made the answer harder to find, I rewrote it. That was the whole rule.

One clean file request flow.

Most tools bury file requests inside email or chat, which is where the follow-ups start. I designed a dedicated flow instead. Single modal, minimal fields, confirmation built in. It’s a small piece of the product that carries most of the promise.

A design system that could grow with the AI layer.

The founder wanted AI to eventually make the system smarter without redesigning around it every time. So I built the visual language and components to hold their weight now, and adapt later. Syne for display, Manrope for body, a set of reusable patterns that would still look right once AI features arrived.

Small moments matter in a “boring” product.

File management sounds dull. It isn’t, if you’re the one waiting on the file. I designed the empty states, transitions, and micro-interactions to reward the person actually using the tool. The moment a file request goes through, they should feel it. That’s the point.

What happened

The design was approved and moved to development. The founder called the work intuitive and considered, and still references the system as the product evolves. The AI layer is being integrated on the roadmap.

Looking back

Oploads taught me that some of the best product decisions look like nothing on a screenshot. The reason the file request flow feels easy is that a lot of choices were made about what to leave out. You can’t screenshot restraint. But you can feel it when you use the thing.

That’s stayed with me. The best product design isn’t the loudest work in the room. It’s the work that gets out of the user’s way and lets them keep going.