How do you even pronounce syncplicity? Dropbox is a nobrainer in just about every language that is somewhat relevant on the internet for commercial reasons, that alone would give them an edge. Sycn?what? Oh, never mind, I'll just use dropbox. Cutesy names are rarely worth the downside. Keep it short, simple, easy to spell and pronounceable in an un-ambiguous way. Or you'll never even get to the point where you have t…
I'll download anything with a crappy name as long as the functionality is there. I really couldn't care less. Do I really think Apple is a great name for a computer manufacturer? Definitely not on the surface. But they ran with it and now it's accepted as one of the strongest brands on the planet.
Why Dropbox Succeeded and Syncplicity Didn’t
31–40 of 70 posts
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#32People can edit Google Docs with Office, and Office with Docs. No need to choose one.
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#33When I can't get something right, I keep on trying. Maybe not always a good idea.
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#34To be fair, most companies that complicate their feature set don't do it because they enjoy writing more code. It's just difficult to focus on your core competency when a simple product sounds boring on paper. It's so much harder to pitch to a VC or potential employee. Who wants to support a product that's just going to sync one folder instead of your entire system? But it's always the companies that manage to make it through that stage that succeed.
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#35How do you even pronounce syncplicity? Dropbox is a nobrainer in just about every language that is somewhat relevant on the internet for commercial reasons, that alone would give them an edge. Sycn?what? Oh, never mind, I'll just use dropbox. Cutesy names are rarely worth the downside. Keep it short, simple, easy to spell and pronounceable in an un-ambiguous way. Or you'll never even get to the point where you have t…
I'll download anything with a crappy name as long as the functionality is there. I really couldn't care less. Do I really think Apple is a great name for a computer manufacturer? Definitely not on the surface. But they ran with it and now it's accepted as one of the strongest brands on the planet.
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#36Earlier quoted context omitted.
I'll download anything with a crappy name as long as the functionality is there. I really couldn't care less. Do I really think Apple is a great name for a computer manufacturer? Definitely not on the surface. But they ran with it and now it's accepted as one of the strongest brands on the planet.
Hard to find a more universally understood symbol in the western world other than the cross (and that's a bit much for a computer company). I think it was an excellent choice.
Sun!
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#37Earlier quoted context omitted.
Hard to find a more universally understood symbol in the western world other than the cross (and that's a bit much for a computer company). I think it was an excellent choice.
> Hard to find a more universally understood symbol in the western world [...] Sun!
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#38Re: Why Dropbox Succeeded and Syncplicity Didn’t
#39It's so easy to overlook the benefits of staying obsessively focused. Quickly though, almost in your back, each single bit/feature/line of code added to the mix multiplies with the others, and it's over already.
Non-programmers tend to think that adding a software feature is akin to adding on to a house. Sure, it take some effort and money, but the resulting house is surely better, right? (This isn't always true, of course, but still) In reality, adding a software feature is often like adding onto a house in the center of it, expanding the rest of the house around it to make room. Suddenly the job looks a lot tougher.
Re: Why Dropbox Succeeded and Syncplicity Didn’t
#40Earlier quoted context omitted.
Thanks for linking to the original. There's some real gems in here from the founder of Syncplicity. For instance, not having a Mac client meant that the tech press wouldn't touch it. Then, they wouldn't write about it. That's pretty enlightening.
It is a little contradiction to the statement "My philosophy is that they're right if their feature request is right only if it works for 80% of your customers." . Apparently sometimes a small minority of customers still can make all the difference.
Leaving out Mac support in this case is like opening a coffee shop that sells $4 lattes, but can only be reached by people driving beat-up old Fords and Chevys.