Dropbox (YC S07) Announces 4 Million Users, Hires A VP From Salesforce
techcrunch.com
techcrunch.com
Dropbox helped me convince my old boss that I could work from home.
I use Dropbox to back up my iTunes music library...for some reason I used to lose a lot of my music every time I got a new computer.
All my work and personal files can be accessed and emailed right from my iPhone.
I sync 4 computers: work laptop, home laptop, a dell zino for my tv and my iPhone. I never have to worry about a thing... Dropbox just works.
Can you talk more about this? How do you use Dropbox for telecommuting and how did you convince your boss it was an effective tool for telecommuting?
https://www.dropbox.com/votebox (API is nr 9)
Although I'm not sure what file system for the web means. I believe dropbox itself stores files in S3.
At least I remember them talking about a plan to allow users plugging their own S3 instance in (that was years ago).
I, for one, am one very happy paying customer too, and have said it more than once.
edit: Not sure why the downvote. "4 million users" can mean pretty much anything.
Just wish articles would quantify what 'user' means when they say "X has Y users".
The web access is great but marginal, for me. It would be a lot better if the default experience was that clicking a spreadsheet or powerpoint opened it in Google Docs (or similar) rather then downloading it.
A web experience on the web and a desktop experience on the desktop.
I think the problem with things like Google Docs (or Zoho, for example) is that they are trying to get you off the desktop. MS wants to keep you on the Desktop. Google might not be highly motivated to sync your spreedsheet to your PC for easy access via excel.
Dropbox might pull off a serious coup if they became the platform agnostic glue. Log in to Zoho, all your dropbox files are available to you. You edit them, they are still available to you via open office, Google Docs, MS Office, whatever.
Google, I suspect, might want the filesystem to be with them though.
I assumed a new global role with my company this month, and the second task I was assigned was 'Register for Dropbox and tell us how we can use it for our 160+ people'. That it was specifically 'Dropbox' shows how a clean and simple service that works easily can make massive inroads.
Short of polling a random sampling of users we probably have to hear from dropbox for those numbers.
From the responses in the votebox it sounds like its not a priority for them, so thats why I left.
Disclaimer: I work for http://www.humyo.com/
Humyo is not as well-known as dropbox (especially in the US) but we have a significant userbase (>500k) and are I think fairly feature-rich. (e.g. We've got a number of the top-requested features on dropbox-votebox already implemented, have Zoho integration, versioning, recyclebin, WebDAV access). Have you considered and discounted us or have we not made ourselves known to you?
There are two schools of thought - "more features == better" and "fewer features == better focus on important features == better". I'd appreciate others' thoughts on this. Is the humyo featureset: 'good' or 'too confusing'? (or is there some other turn-off on the humyo site/signup process)?
(I've held off commenting on other dropbox threads since I don't want to spam HN with what might be seen as an advert, but since this sub-thread is about featureset I'm interested in the comparison.)
I could use read-only sharing permissions as well. It would avoid me situations where my boss moves files on his desktop away from Dropbox or add a full application to a shared folder…
Hackish parts: 1. The email format could change. 2. If the folder name isn't unique the email contains the non-unique name. Eg "ourdoings" in email, then when I accept, the folder is named "ourdoings (28)". I have to change the folder by hand. 3. They have to use the same email for dropbox and ourdoings signup. 4. Often people make subfolders of their "Photos" folder which doesn't fit the workflow.
There are changes I could make to help address these issues. It just hasn't been a high priority. The system works great once setup is done. I'm really glad I implemented it rather than just wait for an api. There's no more convenient way to upload photos.
I currently use git for versioning but i've though about trying to do a build for mediatemple to use that for deployment and updating some of our smaller web clients where git is overkill.