Genesis of requiring a "Dropbox folder," versus designated folders

Re:Genesis of requiring a "Dropbox folder," versus designate... by SoftwareMaven on Thursday April 28, 2011 @04:19PM (#2494929)

The core take-away from this, especially for the early startup, is doing less better is a far superior strategy to doing more worse. At the early stage, nobody is going to care about how many features you have. They care about how well you solve the small problems you are solving.

[ Parent | on HN ]

Re:Genesis of requiring a "Dropbox folder," versus designate... by pufuwozu on Thursday April 28, 2011 @07:37PM (#2495628)

I liked the way Drew put it:

It's also one of our core design principles to do fewer things rather than half-ass anything...

[ Parent | on HN ]

Re:Genesis of requiring a "Dropbox folder," versus designate... by mwbiz on Thursday April 28, 2011 @09:06PM (#2495920)

Totally agree. I would also add that the long-term effect of doing more could have been really detrimental here. If they let users share tons of folders this would have made it much more difficult to work with a variety of platforms and devices. If you don't have to put in a feature, don't!

[ Parent | on HN ]

Re:Genesis of requiring a "Dropbox folder," versus designate... by VB6_Foreverr on Thursday April 28, 2011 @05:22PM (#2495140)

It's not even that, it's KISS for users

[ Parent | on HN ]