Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Developing UI is time consuming and error-prone because it involves <a href="http://en.wikipedia.org/wiki/Design" rel="nofollow noreferrer">design</a>. Not just visual or sound design, but more importantly interaction design. A good API is always interaction model neutral, meaning it puts minimal constraints on actual workflow, localisation and info representation. The main driver behind this is encapsulation and code re-use.</p> <p>As a result it is impossible to extract enough information from API alone to construct a good user interface tailored to a specific case of API use. </p> <p>However there are UI generators that normally produce <a href="http://en.wikipedia.org/wiki/Create,_read,_update_and_delete" rel="nofollow noreferrer">CRUD</a> screens based on a given API. Needless to say that such generated UI's are not very well-suited for frequent users with demands for higher UI efficiency, nor are they particularly easy to learn in case of a larger system since they don't really communicate system image or interaction sequence well.</p> <p>It takes a lot of effort to create a good UI because it needs to be designed according to specific user needs and not because of some mundane API-UI conversion task that can be fully automated. </p> <p>To speed the process of building UI up and mitigate risks it is possible to suggest either involving UI professionals or learning more about the job yourself. Unfortunatelly, there is no shortcut or magic wand, so to speak that will produce a quality UI based entirely and only on an API without lots of additional info and analysis. </p> <p>Please also see an excellent question: "<a href="https://stackoverflow.com/questions/514083/why-is-good-ui-design-so-hard-for-some-developers">Why is good UI design so hard for some developers</a>?" that has some very insightful and valuable answers, specifically:</p> <ul> <li><p>Shameless plug for <a href="https://stackoverflow.com/questions/514083/why-is-good-ui-design-so-hard-for-some-developers/516204#516204">my own answer</a>.</p></li> <li><p><a href="https://stackoverflow.com/questions/514083/why-is-good-ui-design-so-hard-for-some-developers/537490#537490">Great answer</a> by Karl Fast.</p></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload