Skip to content →

Tag: Dropbox

DBX Keynote

My college roommate Eric sent me a link to Drew Houston’s keynote presentation from the inaugural Dropbox developer conference (DBX). While I’m a little sad I didn’t get to attend (*ahem* friends who work at Dropbox who didn’t invite me), I was very pleased to find that some of the major themes of the keynote were very much aligned with some of the things I’ve blogged about recently: mainly, putting together a web file system and creating better synchronized application experiences. While I still have questions about the details on the feasibility of the merge-less syncing back-end they were promising, I hope app developers everywhere pay attention: while DBX might not have gotten as much attention as Google I/O or WWDC, what Dropbox announced is equally important in terms of building the types of services that users will want.

Leave a Comment

Staying in Sync

While I don’t expect everyone to be as device-crazy as I am, one of the obvious consequences of convergence (the idea that more gadgets will become more computer-like — think smartphones, tablets, etc.) is that more people will have more devices. This creates new problems for users who, especially if they are from the US, were previously used to accessing their services/information mainly from a single device. After all, a well-built service or source of information should optimize experience around the user, not which device.

This proliferation is one reason I think internet services like Evernote and Gmail took off: for someone working with multiple devices, its much easier to make sure every device has access to the same data and functionality when the data and functionality aren’t on the devices themselves but hosted somewhere “in the cloud.” (Thank you, Dilbert)

188737.strip

The same logic applies to syncing services like Dropbox and applications like Netflix and smart syncing software like Chrome: they make it easy to ignore which device you’re using and just focus on the functionality and data that you want access to (in the case of Dropbox, its files; in the case of Netflix, its your viewing history and your place in a given video; and in the case of Chrome, its browser history and preferences).

Its gotten to the point where there are enough app developers and technologists working on this type of syncing that I get disappointed when a service or application fails to intelligently think about syncing as a way to delight the user. For instance, I get regularly irritated by the Twitter app for not tracking which interactions (@replies, favorites, re-tweets) I have previously seen. As I routinely move from one device (a smartphone) to another (a PC) to yet another (a tablet), with each device, I need to recheck which tweets and interactions I have seen and which I haven’t. While this is hardly the end of the world, it is only obvious because apps like Google’s new Hangouts app and Amazon’s Kindle app pass information on what you’ve seen and to where between devices, making it a coherent service completely unchained to the specific device you’re using – you can start a chat/book on one device and transition to another device without a hitch. I especially am a fan of Hangouts’ extra step: if you see an incoming message on one device, it will remove the notification from all the other connected devices (and will even minimize the open windows in other Chrome browsers).

This sort of abstraction is a common theme in the technology industry – where new companies and technologies emerge to simplify new sources of complexity. Its something I believe is becoming key functionality as the underlying problem (people with lots of devices and lots of services) grows. My advice to developers and entrepreneurs out there: don’t assume your users are married to any particular device and help them stay in sync. They will reward you for doing so.

One Comment

Why Comparing Google Drive to Dropbox is Missing the Point

Last week, Google unveiled its long-rumored Google Drive product with great fanfare. While the gaggle of tech journalists/bloggers issued predictable comparisons of Google’s new service with online storage/syncing services like Dropbox, I couldn’t help but think that most of the coverage missed the point on why Google Drive was interesting. Yes, its another consumer-facing cloud storage service – but the really interesting aspect of it is not whether or not it’ll “kill Dropbox/Box.net/iCloud/[insert your favorite consumer cloud service here]”, but the fact that this could be the beginning of a true web “file system”.

I’ve blogged before about the strengths of the web as a software development platform and the extent to which web apps are now practically the same thing as the apps that we run on our computers and phones. But, frankly, one of the biggest things holding back the vision of the web as a full-fledged “operating system” is the lack of a web-centric “file system”. I use the quotes because I’m not referring to the underlying NTFS/ExtX/HFS/etc technology that most people think of when they hear “file system”: I’m referring to basic functionalities that we expect in our operating systems and file systems:

  • a place to reliably create, read, and edit data
  • the ability to search through stored information based on metadata
  • a way to associate data with specific applications and services that can operate on them (i.e. opening Photoshop files in Adobe Photoshop, MP3s in iTunes, etc)
  • a way to let any application with the right permissions and capabilities to act on that data

Now, a skeptic might point out that the HTML5 specification actually has a lot of local storage/file handling capabilities and that services like Dropbox already provide some of this functionality in the form of APIs that third party apps and services can use – but in both cases, the emphasis is first and foremost on local storage – putting stuff onto or syncing with the storage on your physical machine. As long as that’s true, the web won’t be a fully functioning operating system. Web services will routinely have to rely on local storage (which, by the way, reduces the portability of these apps between different machines), and applications will have to be more silo’d as they each need to manage their own storage (whether its stored on their servers or stored locally on a physical device).

What a vision of the web as operating system needs is a cloud-first storage service (where files are meant to reside on the cloud and where local storage is secondary) which is searchable, editable, and supports file type associations and allows web apps and services to have direct access to that data without having to go through a local client device like a computer or a phone/tablet. And, I think we are beginning to see that with Google Drive.

  • The local interface is pretty kludgy: the folder is really just a bunch of bookmark links, emphasizing that this is a web-centric product first and foremost
  • It offers many useful operating system-like functionality (like search and revision history) directly on the web where the files are resident
  • Google Drive greatly emphasizes how files stored on it have associated viewers and can be accessed by a wide range of apps, including some by Google (i.e. attachments on Gmail, opening/editing on Google Docs, and sharing with Google+) and some by third parties like HelloFax, WeVideo, and LucidChart

Whether or not Google succeeds longer-term at turning Google Drive into a true cloud “file system” will depend greatly on their ability to continue to develop the product and manage the potential conflicts involved with providing storage to web application competitors, but suffice to say, I think we’re at what could be the dawn of the transition from web as a software platform to web as an operating system. This is why I feel the companies that should pay more close attention to this development aren’t necessarily the storage/sync providers like Dropbox and Box.net – at least not for now – but companies like Microsoft and Apple which have a very different vision of how the future of computing should look (much more local software/hardware-centric) and who might not be in as good a position if the web-centric view that Google embodies takes off (as I think and hope it will).

2 Comments