Disparate Matters

Building Slick Apps

I've long struggled, when building an MVP or a v1 of a new application, with paring down my featureset to a scope that allows me to implement it to a degree of finish that I am content with.  I'm well aware of all the advice akin to Reid Hoffman's, "If you aren’t embarrassed by the first version of your product, you shipped too late."

Basecamp's approach of building half a product, not a half-assed product, while helpful in making it explicitly clear you are allowed to deeply cut features, is not exactly how I look at things.

So it was with great delight that I recently stumbled upon Jason Cohen's description (from way back in 2017!) of a SLC ("slick") product.  This is what I aim to build.

A product that is narrowly-focused (simple) on a core purpose, pleasant to use (lovable), and has everything you need to accomplish what you set out to, but nothing beyond that (complete).

This just feels right to me.  It's liberating to know that you are only going to make your product worse if you keep polishing it.  Is it easy to use (and to figure out how to use if you are new to using it)? Does it look "nice" and is it pleasant to interact with? Does it do only what it must? Then it's slick; ship it.

All Posts