Do you think early users care about design or just function?
by•
I’ve been thinking about how much design quality actually matters in the earliest stages of a product.
Some users don’t seem to mind rough edges if the tool genuinely solves a problem. Others instantly bounce if the UI doesn’t feel “trustworthy.”
As founders, we often obsess over every pixel but maybe early adopters just want momentum and clarity.
What’s your take?
Would you rather ship a rough MVP fast or delay for a polished first impression?
730 views
Replies
I’d ship fast and validate the idea first.
Makers Page
@nikki_domingo Same here. Better to validate early than polish something nobody wants. You can always refine after learning from users.
Actually it depends upon who these early users are, users who need it the most won't care about UI as their current need, or say problem depends upon the product, so however it is they will use it. But those who need it, but even are okay without it they need UI cause kind of like they need more factor to compel them to use the product.
Rough MVP is much better but only in a condition when one could reach fast to the users who need it the most else at the end it to gonna waste the time, and actually a huge lot of time.
Makers Page
@seekerx010 That’s a sharp observation. The “must-have” crowd tolerates roughness, but the “nice-to-have” crowd needs persuasion through good UX. Reaching the right users early makes all the difference.
I find it's better to ship fast vs delay and polish. Early user feedback is priceless, and if you're working closely with them they'll be quick to forgive any rough edges.
Makers Page
@vsteppp Totally agree. Early feedback beats perfect polish every time. When users feel part of the process, they care more about progress than perfection.
After 15 years in tech, I have seen the evolution in term of what people wait for in term of design, UX, brand and the level is far higher than before to convince people
We shifted from building MVPs to SLCs a few years back for our clients after reading this article. https://longform.asmartbear.com/slc/
As a product builder, its a happy middle ground. Its the least amount we can do to look and feel good.
Hot take: early users don’t need a velvet couch—they need a chair that doesn’t wobble. But if the screws are labeled and the instructions aren’t hieroglyphics, they’ll sit longer and tell friends. Clean beats cute, clarity beats chrome, and momentum beats minimalism posters.
Most often, you cannot separate function from design. Design supports the function. If the function is to cancel an order or to approve an invoice but it is not well-designed (users are not sure, the message is unclear, the steps for specific use cases are missing)—then the function does not serve the purpose. Product teams should see these collectively and not function vs design.
relayd
I feel like, the design and polish should match the app.
If my goal is to build a high quality productivity app, I should make sure the design reflects that.