UI Past, Present, Future

Question

I give a short discussion on this issue from the point of view of a programmer. I was thinking about how to talk about 3-axis interface design:

• The closeness . How close the code you write matches the user interface.
• Interactivity . How flexible and powerful the user interface can be.
• Difficulty : how difficult it is to create a user interface (technical / embedded)

Then I was going to discuss the following user interfaces:

• Command line:

  High proximity, somewhat high in complexity, low interactivity

• VB / MFC / Windows Forms

  Low proximity (work with large API / controls / user interface model), medium interactivity - you can create it, but with a high penalty in the immediate vicinity (third-party libraries / controls), a larger range in complexity; simple applications are easy to create.

• Web

  Low proximity (the browser does work with legs, different browsers behave differently), high level of interactivity (DOM / CSS / Javascript / Browser), high complexity (many moving parts)

• Silverlight (possibly other RIAs)

  Higher proximity than RAD / MFC / VB, as well as Web-style interfaces, high interactivity, lower complexity (for example, animation in this environment compared to OpenGL, etc.)

Questions

• 3 ? , , , , , , , .

• , ?

• , (RIA ..)

• (+/-)

Answer 1

, , , ?

, - , ( ) . Progammability, , , , , Dev , VB.

Answer 2

, . .

Answer 3

For the axis of interactivity, I think that usability should be used because flexibility and power are useful because they make the user interface more convenient. The user must quickly determine how to use the software, it should be intuitive.