Huddle’s confusing nomenclature

In SharePoint, if you want to edit a file, you check it out.  And when you’re done, you check it back in.  It makes sense.  It works.

In Huddle, if you want to edit a file, you lock it.  And when you’re done, you unlock it.  I find this far more confusing.

I understand the rationale for Huddle’s choice in nomenclature.  In locking a file, you are preventing other people from editing it.  And when you unlock it, those with permissions are again entitled to edit it.

But it would make equal sense to me if the terms were reversed.  I might unlock a file to edit it—just as I would unlock a bike to ride it—and then lock it when I’m done.

The terms they’ve chosen result in a slightly confusing user experience.


One Response to “Huddle’s confusing nomenclature”

  1. Joe Harris on July 20th, 2010 10:44

    I’d be interested to know how you’re using Huddle.

    I’m working on a project to provide a sort of data warehouse & reporting / backup & archive web app for very small businesses (or a single team). The focus is on gathering data from web apps (via APIs) rather than local apps (via SQL).

    Do you use any other web apps: e.g. FreshBooks, RescueTime, etc.? Do you ever bring the data from various web apps together (in Excel maybe) or wish you could?


Leave a Reply