3 Comments

  1. Most of the advantages you stated are also the advantages of command line interfaces. However, command line interfaces were BEFORE the graphical interfaces and was made for “the common user” – CLI was less inviting.

    What’s changed? Why do people love textual applications again? It’s it because using computers, and mainly typing on keyboard became such a basic task?

    Do you think that chat bots will make CLI more common? Should I target my future apps to provide an interface using “CMD” and “Terminal.app”? After all, if you take out the “chats” with real people, the “bots” are nothing more than a textual utility.

    • omritzek

      I think CLI’s and chatbots are different in their essence.
      CLI’s have a “Power User” vibe. The common user will find a CLI interface kind of intimidating.
      A chatbot tries to copy a human tone, while CLI is pretty mechanic.
      I think the decision (like all UX decision) should be based on who are your users. For common and un-technical users (let’s say, my mom), I’d go for a chatbot, but for “Power Users”, who get excited from keyboard shortcuts and optimization (of power, finger movements, etc.) CLI’s are awesome and truly fulfilling.

      • Then maybe our interfaces could be better. There are indeed applications that should keep the super user vibe, but we CAN think of a way to build other application levels. Therefore, with the right ux design, command line applications can help us make normal users to super users, over time.

        An example could be the simple gif not. “gif me” can, and should be, a command on Apple’s spotlight search. Just trigger CLI apps, and make better experience for inexperienced users to make them comfortable with the environment.

Leave a Reply

Your email address will not be published. Required fields are marked *