Comparing Collaborative Web Services
Buying the vast feature set of a collaboration server like Microsoft Office Sharepoint would be overkill for many businesses. That's why Sharepoint has lots of competition from Web-based services that offer more-focused subsets of collaboration tools for fewer dollars, and in some cases for free. We looked at four alternatives to Microsoft's monolithic server: Central Desktop, Ninian Solutions' Huddle, 37Signals' Basecamp, and WebEx's WebOffice. All four provide basic document management or sharing capabilities, user management and communications, and project management tools. A couple even offer features--such as app sharing and chat--that are well suited to geographically dispersed work groups.
What's Up, Docs?
You don't need a specialized service if you just want to share files with others on the Web; various services, including Google Docs, give lots of upload space and the ability to share uploaded files with fellow users of your choice. But Google et al. don't offer document management, in which the service tracks versions of documents and uses a check-in/check-out system to protect master documents.
Huddle (even the free version) has the most thorough controls for document management. Huddle users can check out and download documents for editing or proofreading, upload and check them back in when finished, and then assign document review and approval duties to other team members. In contrast, the free, limited version of Basecamp won't permit file uploads; paid versions offer file storage with basic version tracking but no check-in/check-out capability. Central Desktop falls in the middle, allowing you to set a document's status manually as Draft, Pending Approval, Approved, Final, or Cancelled. WebOffice, which starts at $60 a month for five users, doesn't track changes in uploaded documents at all. But it does let you configure Windows Explorer to upload and download files to and from the WebOffice documents folder.
In all but WebOffice, users can create and collaborate on simple text documents directly in the service's interface--a nice way for users to author drafts of text collectively for later publication. Unfortunately, though all three text-edit utilities worked fine, each suffered from a common collaboration flaw: Attempts to edit a document that another user was editing simultaneously generally resulted in the loss of the edits of one or both users, with little warning in advance from the Web site. We don't understand why the three services don't simply prevent users from editing already-open documents.
Comparing Collaborative Web ServicesNext Page