You’ve been there. You download the new, highly anticipated app. It has beautiful gradients, buttery animations, and a UI that would make Apple jealous. And then you try to actually use it, and it fails. The core feature breaks. The sync lags. You close it, never to return.
Contrast that with Iroh Drop, a tool I recently stumbled across. The UI? Unforgivably rough. It looks like a developer built it at 2 AM after three cups of bad coffee. But it did exactly what it promised. It transferred the files. It worked.
Beauty doesn’t solve problems. Utility does.
The top comment on the site said it all: “Site is a little unpolished to me, but it works so +1.” That is the ultimate compliment for an early-stage product. We are so obsessed with pixel-perfect designs that we forget the only metric that matters in the beginning: does the damn thing work?
Product teams miss this completely. They spend weeks tweaking the drop shadows on their SaaS dashboard while the core API leaks memory. They over-invest in superficial refinement before validating core functionality. They are painting the walls of a house with no foundation.
A perfectly designed button that crashes the system is worse than a text link that actually works.
Early adopters don’t care about your font choice or your seamless onboarding flow. They care about the relief of finding a tool that simply works, even when it looks rough. They are pragmatists. They will trade aesthetics for reliability every single time.
If you are building something new, stop obsessing over the aesthetics. Ship the ugly thing. If it solves the problem, people will use it. If it’s beautiful but broken, they will leave. Stop painting the walls before you’ve poured the foundation.
FAQ
Q: But won't an ugly UI drive away mainstream users?
A: Yes, eventually. But you don't have mainstream users yet. You have early adopters who care about solving a specific pain point. Optimize for them first, polish for the masses later.
Q: How do I know if I've validated core functionality?
A: When users start using it repeatedly despite its rough edges. If they complain about the UI but still log in every day, you've got product-market fit. That's your signal to start polishing.
Q: Is design completely useless then?
A: Design is crucial, but it's a multiplier, not the base. If your core utility is zero, multiplying it by beautiful design still equals zero. Build the engine before you paint the chassis.