Someone looked at their signup flow and asked the comments whether it needs a designer.

What a half-built product sounds like in a design tutorial’s comments

Nobody searches for a UX designer. They search for how to make an app look professional, how to lay out a dashboard nobody has to be taught, why people reach the second screen and stop. Then they follow along with somebody arranging a clean example in a tool they half know, pause it, and type their own product in underneath: the signup flow, the number of screens, the launch date that has moved twice. What they’ve typed is a scope of work, handed over for nothing, before a single call has been booked.

On the newest pass, twenty-four of the forty-five lit cells were people partway through deciding to do it themselves: a design file open beside a half-built product, the tutorial paused on a color style, and an honest question about how far somebody who isn’t a designer gets before it starts to show. Fifteen had stopped weighing anything and described the damage instead: people signing up and never returning on day two, a support inbox that keeps asking where a button is, and software that works perfectly and looks like a spreadsheet with ambitions. Five skipped the method entirely and asked for a person: who reworks an app that already ships, what a signup flow costs to redo, and whether anybody takes on a project this small. One had paid a designer once already and got back a beautiful file nobody on the team could build from. The three want different things from a reply. Somebody still learning needs to hear which part of this a tutorial will never reach. Somebody counting lost signups wants a number, and the weeks it takes to move it.

Filling the space around them are plug-in recommendations, people asking which typeface that was, the standing argument about whether a design system matters at this size, and several hundred comments saying clean. At one-to-two, somebody shipping to paying customers and somebody building a first side project type the same two sentences, which is the entire reason all 70 get read.

Where to find UX design clients on YouTube

The uploads divide into four shapes, and only one of them is all designers. Tutorials aimed at people who are not designers are the richest seam, because everybody underneath has a product they’re trying to draw themselves and a growing suspicion about how that’s going. Videos about why an app loses users gather the founders who already know something is wrong and have a figure for it, which makes their comments the most answerable on the platform. Landing page and conversion walkthroughs pull in people who will pay for one screen long before they’ll pay for twenty, and one screen is how most of this work starts. Portfolio reviews come last, since nearly everybody under those is already in the trade. The marketing site out front, rather than the screens behind the login, belongs to the page a stranger sees before they sign up. A checkout leaking customers the way a signup does sits with the last three steps of a store. The logo argument that arrives halfway through every redesign is a separate job, over in the part of this that is about the name.

The comment that wins the project names the screen they are losing people on

Somebody who has typed their signup flow into a comment box has two questions underneath it, and a portfolio grid answers neither. The first is whether design is the problem at all, since half of what looks like a broken interface is a product asking for a decision too early. The second is what it takes to put right, in weeks and in money, because everything quoted to them so far came from an agency pricing a quarter. Both fit in a reply. Name the screen you would change first and what it’s costing them in the figures they already gave you, say how long that one change takes on its own, and say plainly which of their problems no redesign is ever going to solve. Giving the diagnosis away in public feels like running the kickoff meeting for nothing. It is also the only reply in that thread written by somebody who has shipped a product rather than a mockup.

What finding clients on YouTube actually costs you

Call it three comments, and the morning is still intact, which is less time than one call that ends in maybe next quarter. It slips anyway, because every other hour of this work is attached to a file with a date on it and this one is attached to nobody. A finished flow ends in something a developer can build. A handoff ends in a link somebody opens. Four weeks of good comments end in nothing anybody reviews, so it drops behind the sprint that started Monday. Meadowrank makes it countable. A comment with a product behind it is held under a short match-3 board. The cover clears, the card opens, and there is the upload it was left beneath, the numbers they typed in, and a reply written the way you talk in a first call about somebody else’s product. On a day given over to revisions, the feed lists the same signals for a little less XP, so an afternoon with no gap in it still counts. Points only ever come from replies you actually sent, so the total at the end of a month counts founders you wrote to, not videos left open in a background tab.

Playing costs nothing, and free here means the finished game rather than a locked-down slice of one: the board, the feed under it, the streak, and five cards dealt each morning out of the pool everybody works from. $35 a month, or $350 across a year, swaps that shared pool for a Quarry nobody else digs in, and the scan then follows the kinds of product you’re quickest on, the stage of company that can decide inside a week, and the uploads their founders actually watch.