From my .Net developer's point of view, I am not seeing why these aren't just weak versions of the Azure storage capabilities or Amazon's S3. It's nice to be able to target DropBox as a storage location but that's a pretty rare use-case for me. Especially since their security store is incomplete.
Dropbox has done a phenomenal job of taking a complex challenge (file sync) and making an incredibly simple user experience. Extending that strategy into other common tasks with new and purchased apps could be very successful. The big element missing is BaaS (back-end as a service) for data and events that aren't files. Given the poor track record of services like iCloud, you can imagine a lot of developers adopting the Dropbox API and in a few years most iOS devices might be running a combination of official Dropbox apps (replacements for itunes, mail, and maybe calendar) and many other essentially stateless apps that use the Dropbox API for sync and storage.
In the short term this could be very convenient for users and developers, but in the long run it creates another monolithic, centralized platform. This kind of functionality needs to be delivered as a protocol so users can choose service providers who compete on price, features, and privacy instead of being citizens of a particular platform (Facebook, Apple, Google, MSFT, or increasingly Dropbox).
How would this benefit dropbox?
Isn't it a platform on a platform at that point?
Assuming that the "1 billion" refers to number of sync events, that statistic implies that on average, Dropbox users only make changes to ~6 files in their Dropbox per day.
That doesn't make any sense at all. Dropbox must have a massive Power Law at work.
EDIT: I might be wrong with my interpretation of "files synced": it could mean distinct numbers of files that receive a sync event atleast once per day or files added per day to a Dropbox which are then synced. In both cases, I believe the ~6/day statistic and I apologize.
I believe it. Maybe I'm an outlier, but I usually only write to a few files from Dropbox in any given day. I read those files often, but I rarely write unless I'm doing something like uploading pictures from my camera.
I store my IM logs in my Dropbox. Every time a message is sent, 2 files are changed (the message log and the overall database). One conversation alone can fire 100 sync events.
And if you're like me and are a Ctrl+S addict when working on important papers or code, each Ctrl+S is a sync event.
Now, there's nothing in that which justifies having a developer conference. I definitely do not understand that. But the Dropbox service itself deserves the praise it gets.
I only got dropbox installed on my PC because we needed to exchange some files with an external contractor that only used Dropbox.
As soon as the project was finished I removed it from my PC.
I love the idea of cloud apps that use user-provided datastores. It makes it both cheaper for a startup (because they can crowdsource their data storage) and easier for users to control what data services have about them. Google Drive already provides a service whereby I can store a user's data in his Drive account without cluttering his filesystem with my app's metadata. Dropbox Datastores sounds like a similar feature, but it's way less appealing to me if I can't talk to it from my backend.
I look forward to kicking the tires, since I've been looking for a solid replacement for Parse ever since Facebook bought them.