Dribbble taught a generation to design for other designers

Open Dribbble on any given afternoon and you will find a food delivery app screen with a drop shadow so soft it looks lit from inside, a colour palette that took real skill to balance, and absolutely no information about whether the app works. No flow, no other screens, no indication of what happens when you tap the big orange button. It has four hundred likes. Somewhere else on the same page is a fintech onboarding screen with the same treatment — glass card, gradient mesh, a number climbing in a font that costs money to license — and it has the same problem. You cannot tell if either one shipped, because shipping was never the point of the image. Looking good in a square crop was the point, and on that count both succeed completely.

That is not a complaint about the work. The craft on Dribbble is frequently excellent. The complaint is about what the format trained an entire generation of designers to make, and to think a portfolio was for.

The fix for that is not complicated, but it does need a page you actually control, and building one used to be exactly the kind of project people put off in favour of one more shot: draft it, mean to finish it, never publish it. reach exists to remove that specific friction — you upload the CV you already have and a photo, and it composes a finished one-page site in about twenty seconds, live on a free yourname.joinreach.app subdomain in under two minutes. That is useful for exactly one page: it makes one index.html with no sub-pages and no CMS, and you cannot point it at a domain you already own — the only way to a custom domain is buying one through reach. But one page, argued properly, is precisely what the rest of this piece is going to make the case for.

The shot decides what gets made, not just what gets posted

A shot is a single image, roughly landscape, viewed at a fixed size in a feed next to other shots competing for the same half-second of attention. That constraint sounds neutral — every platform has one — but it is not neutral at all once you notice what it selects for. A shot rewards colour, contrast, and a hero moment that reads instantly without context. It punishes anything that needs a second screen to make sense: a form with validation states, an empty state, a settings page, the unglamorous ninety percent of a real product. Nobody wins Shot of the Day with a well-considered error message.

So designers, being rational about where the attention is, started building for the shot rather than building a product and then photographing a piece of it. The isometric illustration trend, the neumorphic soft-UI phase, the endless parade of dashboard mockups for companies that do not exist — these were not accidents of taste. They were the correct response to a scoring system that pays out on a single frame with no functional requirement behind it. A designer optimising for likes on a five-second glance will converge on the same visual moves as everyone else optimising for the same thing, which is part of why so much of the platform looks like one enormous mood board rather than a record of shipped work. The format did not just influence how work was presented. It influenced what work got made in the first place, because a large share of what appears on Dribbble was made specifically to appear on Dribbble.

Peer approval and client evidence measure different things

The people liking a shot are, overwhelmingly, other designers scrolling for inspiration between their own projects. That is a fine audience to have and a genuinely useful one — you learn things from what other people are trying — but it is not the audience a portfolio exists for, and the two audiences want opposite things from an image.

A peer wants an idea worth stealing: an interaction pattern, a colour combination, a typographic trick. They reward novelty and polish because that is what is useful to them, and they reward it in about the time it takes to scroll past, which is not enough time to evaluate whether a decision was any good, only whether it looks confident. A hiring manager wants the opposite thing entirely: not an idea to borrow but evidence that you can be trusted with their actual, current, unglamorous problem. They want to know what you chose when the obvious option and the right option were different things, and what it cost. That is exactly the information a shot format cannot carry, because a shot is outcome without constraint — a screen with the client, the deadline, the accessibility requirement and the stakeholder who hated the first three directions all edited out. Two designers whose actual jobs look nothing alike can produce shots that are visually interchangeable. The metric that scores well on Dribbble and the metric a reviewer is actually applying have almost no overlap, and a portfolio built entirely for the first one answers a question nobody hiring you is asking.

What it genuinely gave people who had nothing else

Here is the part that is easy to skip past when making this argument, and shouldn't be.

Before Dribbble, a huge number of designers worked in total isolation from any local peer group — one designer at a small agency, the only person doing this job at a regional company, someone self-taught with no design department to learn from. For that person, Dribbble was the first place they could see, honestly and continuously, what good current work looked like, and get direct feedback on their own from people who actually did the craft rather than a manager who couldn't tell competent from excellent. That is a real service and it is not a small one. It gave isolated designers a shared standard to measure against, which is a thing almost every other field provides through proximity — a studio, a newsroom, a trading floor — and design didn't reliably have until a feed made it available to anyone with a login. Plenty of careers got better because of that, including some that eventually moved past the platform entirely. It is worth saying plainly: the same format that produces a weak portfolio can be an excellent practice ground, and those are not a contradiction.

The portfolios that recovered, and what they actually changed

The designers who moved past a Dribbble-only presence didn't do it by making better shots. They did it by adding a layer the shot format cannot hold: the writing. A page that says what the constraint was, what was tried and rejected, what shipped, and what happened after — the exact material outlined in the case for the portfolio that gets you hired, which is the decision, not the artefact. The image usually stayed. It just stopped being the whole argument and started illustrating one.

The second thing that changed was where that writing lived. A shot embedded in someone else's feed, sitting between two other people's projects, cannot hold a paragraph of reasoning without breaking the format it depends on — that is precisely the trade-off we go through in Behance versus a portfolio on your own domain, and it applies here with less ambiguity, because Dribbble was never designed to hold prose at all. The recovered portfolios moved the case study somewhere they controlled the layout, kept a Dribbble profile pointed at that page rather than trying to compete with it, and used the platform for what it does well instead of asking it to do the one thing it structurally cannot.

Where the shot still is the job

None of this means the format is wrong for every kind of hiring. For roles where the visual genuinely is the deliverable — icon sets, illustration, motion loops, the kind of production-grade UI polish where the client is buying exactly the texture and finish a shot can show — a well-made Dribbble shot is close to the actual work product, not a stand-in for it. A studio hiring an illustrator to draw consistent icons at a consistent weight is evaluating almost exactly what a shot shows them. That is a narrower slice of design hiring than the platform's traffic would suggest, but it is a real one, and inside it the shot format is not a distortion. It is just the format the job happens to require.

The better use is a sketchbook, not a shopfront

The honest reframe is to stop asking a shot to do a case study's job. Post explorations, half-finished ideas, the version of a screen you're not sure about — the same instinct that made a physical sketchbook useful, applied to something that gets feedback in minutes instead of never. That is a genuinely good use of the format, and it is compatible with also having a real portfolio, on a page you control, that does the slower work of explaining what you decided and why — the kind of page we go through building in a personal website for designers. The two are not competitors. One is where you think out loud. The other is where you make the case. The mistake, and it is a common one, is letting the first one stand in for the second because it already had an audience.