I know this is against the grain, but Dropbox replaced SVN for our development projects. It's a lot easier for designers to use... SVN is too tedious.
One fundamental difference is that Dropbox syncs things between drives and cloud. Zumodrive only uses your local machine as cache. The difference is when you have 20 gigs in the service, a Zumodrive doesn't actually use up any of your HD space. On the other hand, you don't have to be connected to the internet to see/edit your Dropbox files, only to sync.
I'd:
* Rebrand Zumodrive as a future version of Dropbox
* Use Dropbox's syncing model to ensure the local cache is kept up to date to a user-configurable percentage.
This would allow speedy access where the local device has the space, and still allow access where the local device doesn't have the space.