đ¨ Do solo makers need a UI/UX designer?
byâ˘
For solo makers, wearing every hat is almost unavoidable - developer, marketer, support, product⌠and often designer too.
AI makes this even easier now. You can generate UI pretty quickly, but a lot of products end up relying on consistent, polished AI-generated solutions rather than something truly unique or thoughtfully designed for their specific product.
So Iâm curious:
Do you design the UI/UX yourself when building solo?
Or do you think bringing in a designer (even for a few key screens) is worth it?
And if youâre using AI for design, do you feel itâs enough to get you to a good product experience?
Would love to hear how other makers approach it.
3.3K views
Replies
Iâd split this into two stages. Early on, I think having a genuinely good UX designer is important. We found one for our project, and it made a real difference, because good UX isnât just about visuals. Itâs about the whole conversation with users, the use cases, and how much a personâs experience can shape the product in ways you wouldnât catch on your own. He really reshaped some ideas about the product itself.
At this point most of the work is UI for specific features and optimizations based on data, A/B testing, that kind of thing. But early on, getting a professionalâs input was worth it.
RunEvr
@alexeyglukharev Nice to hear that a professional touch helped that much!
Are you planning to launch your product here on PH?
RunEvr
@relebohile_motaung Agreed. What are you working on?
AI has made the visual baseline cheap, but it has not made prioritization cheap. For a solo maker, Iâd spend a designerâs limited time on the moments where a confused user can abandon the product: the first-run promise, the decision points, and the recovery states. Everything else can begin with a consistent system and improve through observation. Record a few first sessions and look for hesitation, backtracking, or abandonment; those patterns turn âmake it betterâ into a concrete design brief. That gives both AI output and a designer something real to work from.
RunEvr
@ariajinling Have you ever watched recorded user sessions and realized that the problem wasnât just something to give to the UI/UX designer, but that it actually required changing the backend architecture? =/
And isnât that frustrating?
Solo here. I design everything myself with AI in the loop, and the thing that changed the output quality wasn't better prompts â it was keeping a written design ruleset for the product. Every time a screen gets reviewed (by me, a friend, or a user visibly stumbling), the decision becomes a written rule: what sits on dark backgrounds, what the host is allowed to say, which patterns are banned. AI-generated UI converges to generic when it starts from nothing; it gets surprisingly distinctive when every generation starts from your accumulated constraints.
Where I'd still bring in a human designer: the first version of a pattern that doesn't exist yet. AI-plus-rules is great at consistency and bad at taste-level invention â so a designer for the few screens that define the product's character, then fold their decisions into the ruleset so the next hundred screens inherit them.
RunEvr
@anmol_rerato Great formula: AI + design rules. I can definitely see how that could work at a certain stage of building.
What are you building currently?
Disclosing my bias up front: I'm a product designer, and I also build and ship my own apps solo. So I've argued both sides of this with myself.
Here's how I'd frame it. AI gets you to "not broken" very fast. Like too fast sometimes. User testing gets you from "not broken" to "less confusing." Neither gets you to "right." or 100% lets ship it.
Testing tells you where people stumbled on the thing you built. It can't tell you about the version you didn't build. Nobody in a session ever says "the thing that would have made me stay isn't on this screen" they can't miss what was never there.
That's most of what a designer is actually for. Not making screens pretty. Deciding what belongs on them, what to cut, and what the product's one job is. That judgment comes from having watched a lot of products fail in specific, repeating ways. pattern memory that neither a model nor five test sessions gives you.
So for a solo maker: do the UI yourself, absolutely. But buy a few hours of someone's judgment at the structural moments...before you build, and later when something feels off and you can't name why. That's far cheaper than a redesign, and it's the part you genuinely can't do alone, because at some point you stop being able to see your own product. Especially as a solo founder having to take on marketing, and the many other roles you need to spend time on.
RunEvr
@jdubsss Got your point of view! I think itâs especially difficult when the maker isnât a UI/UX designer. You can have a great idea and build all the pieces behind it, but itâs hard to understand how to bring everything together into one clear and coherent experience. And i think thatâs exactly where your product designer perspective helps - you can see how to connect all those pieces into one whole.
I'm a designer by trade, but the thought of having to design all the various states of my product's UX from scratch was overwhelming. I ended up buying the Untitled UI kit (both Figma and React libraries) and letting Claude use those as the building blocks for my screens.
It would get me 90% of the way there, then I'd go in and polish what needed polishing.
RunEvr
@thomastherhombus I donât mean that if a UI/UX designer creates the design, they shouldnât use AI. Iâm sure AI tools work very differently in a designerâs hands than they do for non-designers.
I often use vibe-coded designs as a skeleton or rough sketch for the actual final design.
So I think your workflow is actually a very modern approach to UI/UX design today.
@adana I've actually noticed this in my own work. A year ago, if I was building something new, I'd probably hire two or three designers for different parts of the project. Now, with AI helping generate concepts, wireframes, and even fairly polished first drafts, that number has definitely gone down. It's kind of crazy how much less design bandwidth I need just to get a product off the ground.
That said, I don't think AI has replaced good designers at all. If anything, it's made taste even more important. Most AI-generated UIs look clean, but a lot of them also look the same. Knowing what to keep, what to throw away, and how to make a product feel intentional is still a very human skill. I think we're going to need fewer designers, but the really good ones will end up being more valuable than ever.
RunEvr
@aamirxv2Â Yes, I agree. Iâve been thinking about this too - if AI is mostly trained to follow existing best practices, I wonder if relying on it too much could actually slow down the emergence of new design directions and ideas. If everyone uses the same âbest practices,â products might start looking more and more alike.
Dinosave
I don't think so
But I'm also a designer lol
RunEvr
@baseddesigner Do you think AI has taken over your profession? =)
I feel pretty good the latest GPT 5.6 Sol with the design skin, it is pretty flexible better than Claude (Fable-Opus) and the latest Gemini 3.7 ihmo. Check the one I did for PolicyWatcher with a dynamic workspace (https://www.producthunt.com/p/policywatcher)
RunEvr
@fabriziodegni Do you have design skills yourself, or are you more focused on the technical side?
@adana Hi Adana, even in the life I have another job :) I am a full stack developer I prefer to manage the whole pipeline by myself.
RunEvr
@fabriziodegni Thatâs the kind of person you are =)
I can imagine youâre more productive working alone than you would be with a team.
What product are you building?
I use stitch for ui mostly...its been amazing and the credits almost seem to never get over
RunEvr
@nivrithi15Â Iâve heard a lot about Stitch too, and even tried it once.
But Iâm not giving up on creating custom UI prototypes for developers just yet! =D