Build Your Own Dropbox Fallacy

When Dropbox launched on Hackernews, one of the top comments was something to the effect of

"why would anyone use dropbox when you can spin up rsync on an ftp?"

This fallacy, prevalent among engineers, shows an undervaluing of ease of use. It also does put value on the time needed to make and maintain a service. In fact, the opposite is true: its quite possible to build a company off of making a simple version of a complex process. examples include:

original HN link

full source quote:

I have a few qualms with this app:

  1. For a Linux user, you can already build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem. From Windows or Mac, this FTP account could be accessed through built-in software.
  1. It doesn't actually replace a USB drive. Most people I know e-mail files to themselves or host them somewhere online to be able to perform presentations, but they still carry a USB drive in case there are connectivity problems. This does not solve the connectivity issue.
  1. It does not seem very "viral" or income-generating. I know this is premature at this point, but without charging users for the service, is it reasonable to expect to make money off of this?

This rhymes with, but is different than not invented here syndrome. Not invented here syndrome is about having a bias towards the build side of build vs buy. This fallacy is about undervaluing simplicity and customer experience.

note to self: is there a better term for this kind of thinking?