But if I had to pick one hardest part, I'd vote for the UI. This stuff, at least the way I'm imagining it, is a significant departure from traditional file manipulation semantics. It's a file system plus the kind of user interactions that "web 2.0" and mobile apps have taught us all to expect. People won't use something that's not both really easy and elegantly designed. And there won't be enough adoption unless there's enough feature set coverage to appeal to lots of slightly different use cases.
I mentioned Dropbox a number of times in the blog post because I think they've done a remarkably good job at both implementation and user experience. That's pretty cool!
It requires a central server, but has a redundancy mechanism built in, in that if server A is unavailable the client simply goes to server B.
It also has a panic password the hides/deletes data with a particular protective marking. Everything is encrypyed, and the server cannot identify any user, even given a user name.
The app can easily be converted to work with files. The thing standing in the way of that is time. I have a four-month-old son that expects board and lodging.
But: 1/ Support on dumb mobile devices is generally quite bad 2/ Caching support is generally quite bad. No connection pretty much means game's over.