search

sanjar-notes / gui-apps

Understand and learn all about GUI apps, from theory to implementation
0 stars 0 forks source link

Polymorphic UIs (AI based), helps everyone on everyform #20

Open sanjarcode opened 1 year ago

sanjarcode commented 1 year ago

A GUI can be considered a "sugary" (for the human 🧠) version of a TUI/CLI.

A static UI works, but opportunity cost for it it high:

  1. You're backend (product/service) is good but UI sucks.
  2. You're product is good but not supported on all platforms
  3. The product assumes a certain knowledge set, jargon and effort from the user.

If the UI is "generated"/"controlled" by an AI (or even a rudimentary selection algorithm) before being presented to the user, this would solve such problems.

A chat prompt seems to be an okayish general UI, but it's slow and too unstructured. Other UIs can be thought of as solutions for this problem:

  1. CLI/TUI - highly structured, very fast. Needs effort initially, least economic (w.r.t usage, effort) on average
  2. GUI - less structured, slow, needs less upfront initially, most economical on average
  3. Chat/prompt - least structured, very slow, least effort needed, don't know economy value [insert]
sanjarcode commented 1 year ago

Note: a GUI will still be needed, atleast for the prompt form. Ignorable.

sanjarcode commented 1 year ago

Use cases:

  1. Super user - wishes to convert this GUI to a CLI/TUI
  2. Normal user - shows normal GUI
  3. Super user in a hurry - CLI with prompt
  4. Normal user in a hurry - GUI with prompt wherever is will speed them up

Goal: improve user experience, radically.

The UI can be version controlled, improved, rollbacked by the user. It morphs on user interaction. If everything breaks down - default to a static UI/CLI with manual control.

MIP: increased indexability. An app, and it's flows can now be indexed, in addition to markup.