In the desktop world, we have the option to use the command line: a uniform interface for a multitude of apps that would otherwise be very different when implemented as GUIs.

Using the same interface, I can move or edit files, cross out tasks on my to-do list, retrieve my password for my email account (using Bitwarden or pass), etc. All in the command line. The GUI for each of those are wildly different.

The other benefit is it is very easy to create a new command line app, as opposed to a GUI.

Is anything like this possible for the smartphone world (even if it doesn’t or will never exist)? What would it look like?

Since smartphone typing is much slower, we can’t simply reuse the command line. We’d need something different. An interface that can still support a various spectrum of different operations, yet ergonomic for a smartphone. What are your thoughts?

    • @matcha_addict@lemy.lolOP
      link
      fedilink
      English
      07 months ago

      As long as the keyboard is constrained by your screen size, the ergonomics in typing speed and error rate are far worse than desktop terminal. If the keyboard is not constrained by screen size, like a sufficiently large physical keyboard, by definition that is no longer a smartphone or mobile phone experience.

      • @Sethayy@sh.itjust.works
        link
        fedilink
        English
        37 months ago

        I think the most confusing part is that you want both the backend and gui to exist, yet don’t like the current back end.

        Realistically you could create some super weird controller using all your sensors at once and just wrap it around termux/adb.

        Things like termux’ first goal is to work both programmatically and via a user, a wheel that would be pretty difficult to recreate just for phones