← Back to home

Accepting eye candy

For some time I’ve been nurturing a pragmatic approach to UI design. Focus on the problem, solve it in the most frictionless way, verify the result, repeat.

My striving for pragmatism and utilitarian design started by two major triggers: reading too much into Lean Startup and Indie Hackers community, but also being tired with the gimmick overflow.

I’m actively pushing back on this extreme in my head these days. I’ve realized that if an MVP solves a problem of a user, it might not solve it after all because user won’t want to use the product. First of all, the app needs to land in user’s hands, and they need to be compelled to stick with it. If a user doesn’t have an incentive to forgive your occasional quirks or even the onboarding process, they will put away your app and call it as they feel it (and not how the software is) — “too difficult”, “too slow”, “not usable” etc.

What I remind myself is that packaging is as important as the product itself. Packaging means the looks of a software product. The more the user is attracted by what they see, the deeper they will dive in the product — “surely there has to be something good in this eye candy.”

Last edited on Jun 14, 2019