1. Enterprise, as someone else mentioned. It's still mostly considered a consumer brand, especially as they've focused on features like photo syncing with mobile phone partnerships. They're an ideal fit for enterprises though and still have huge opportunities.
2. An app platform or what I call "Bring Your Own Data" (not unlike App.net and to some extent Evernote). This is a rising paradigm where users own their data and 3rd-party apps hook into it. Instead of the prevailing cloud model where apps and data are silo'd. An early example is Tunebox, which plays and manipulates MP3s within your own Dropbox instead of hosting them on your behalf. Another example is the way 1Password uses Dropbox to sync data instead of doing its own hosting and syncing.
The app platform is really big as developers don't have to think about syncing. Traditionally data sync has been one of the main benefits of the web. But Dropbox API means developers can write rich, native, apps on any platform and assume the syncing "just works".
This is a bit like the other fork in the road that Twitter walked away from, ie to be the underlying cloud infrastructure for apps. (I wouldn't be at all surprised if Dropbox acquired App.Net or similar to provide a powerful pubsub layer too.) Developers focus on making awesome user-interfaces and delegate all the network infrastructure to Dropbox. That's similar to the way developers can use tools like Firebase and Parse, with the key difference that data resides with the user.
1. Enterprise, as someone else mentioned. It's still mostly considered a consumer brand, especially as they've focused on features like photo syncing with mobile phone partnerships. They're an ideal fit for enterprises though and still have huge opportunities.
2. An app platform or what I call "Bring Your Own Data" (not unlike App.net and to some extent Evernote). This is a rising paradigm where users own their data and 3rd-party apps hook into it. Instead of the prevailing cloud model where apps and data are silo'd. An early example is Tunebox, which plays and manipulates MP3s within your own Dropbox instead of hosting them on your behalf. Another example is the way 1Password uses Dropbox to sync data instead of doing its own hosting and syncing.
The app platform is really big as developers don't have to think about syncing. Traditionally data sync has been one of the main benefits of the web. But Dropbox API means developers can write rich, native, apps on any platform and assume the syncing "just works".
This is a bit like the other fork in the road that Twitter walked away from, ie to be the underlying cloud infrastructure for apps. (I wouldn't be at all surprised if Dropbox acquired App.Net or similar to provide a powerful pubsub layer too.) Developers focus on making awesome user-interfaces and delegate all the network infrastructure to Dropbox. That's similar to the way developers can use tools like Firebase and Parse, with the key difference that data resides with the user.