No completely new advice in this article, but a very good point about design/usability of your first version:
However, your first design shouldn't matter. You should be solving such a huge need that users and customers will do anything to use your product to solve their needs. When your hair is on fire, the look of the firehose doesn't really matter.
If poor usability or bland visual effects push away early adopters, then you haven't actually solved an important problem (at which time you pivot).
As Sean mentions earlier, though:
Not all advice is created equal (...) If the advice doesn't sit well with you, don't blindly follow it
Not all startups are created equal. Not all startups are solving a hair-on-fire problem. Twitter, which he uses as an example later in the article, certainly did not solve any critical problem initially.
