I love the concept of Ubiquity and its "predecessor", Enso. Enso was a great example of empowering the desktop for "experts" by taking advantage of the "appendix" (a latent evolutionary organ you just don't need any more) of the keyboard the "caps lock". Brilliant. The other big advance is the specific implementation of the type ahead functionality within a CLI.
Ubiquity is a tremendous evolution of the CLI concept, but taking it further in important ways. From the End User perspective it is what I have been describing as CLI with GUI support. The other component is the developer framework which makes creating ubiquity commands pretty easy. Now, enough rah rah. This is just an observation within a single space--Twitter. I have noticed that Twitter has been conceived as a CLI. This is b/c it has to all be doable from the SMS API client. Makes sense. However, if you look at the eco-system evolution 2 things have happened: 1) Supporting the CLI are the amazing user driven markup additions like "#" and "@". 2) Almost every major API client has invented a way to do in GUI what previously was purely CLI. I think #1 is just fun and interesting. while #2 is telling about CLIs and their overall utility in the market place. This is my way of saying that I would be cautious to ONLY have CLIs (to the point that someone said earlier about choosing). And if you do have CLIs enable an API system that allows an eco-system to expand over time. CLIs afford markup, so let it happen. -- dave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=40758 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
