1 / 17

Creating User Interfaces

Creating User Interfaces. General issues. Classwork /homework: embedded computing project. Interlude. Use of webcam (getUserMedia) http://faculty.purchase.edu/jeanine.meyer/morehtml5examples.html Why do the mirror?. Cognitive load. What does the user need to know and/or remember?

Télécharger la présentation

Creating User Interfaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.


Presentation Transcript

  1. Creating User Interfaces General issues. Classwork/homework: embedded computing project

  2. Interlude • Use of webcam (getUserMedia) • http://faculty.purchase.edu/jeanine.meyer/morehtml5examples.html • Why do the mirror?

  3. Cognitive load • What does the user need to know and/or remember? • Memory (short term and long term) • Operational skills • ? • Area of active research

  4. Recognition vs Recall • Notion that users can more easily recognize something from a (short) list of options versus recalling. • Less error prone

  5. Refrain on errors • How to prevent? Being pro-active • How to recover • Ways to present possibilities, for example, confirmation operation. • Some errors can be detected by the program, some not. • How to backup efficiently

  6. Network effects • Going from single application on one device to • Application with connections, required or optional with other applications • Example: use Facebook for login (authorization) • May lead to posting information • Example: backup, store, retrieve from iCloud, Google Drive, other • Applications present on multiple devices with some/considerable sharing • Example: Duolingo common status

  7. Network effects Expectations and training; We now are willing and expect to • enter password twice • get option to save password, other information • use dropdown menus • click on maps • More?

  8. Network effects • [Even in these special purpose, embedded applications] • Option in ATM to send receipt using email • Option to set up to always do this. • Option to set up first screen • Other?

  9. Timing • Real-time • Immediately, no perceived delay (latency) • Look up definitions! • Embedded applications often need to be real-time • Database operations • Need to prevent clashes while minimizing waits. • Avoid deadly embrace • Two or more threads each waiting for the other to complete a task

  10. Paying: Now and future • Pay via • Recorded credit card, EFT, Paypay, bitcoin • Pay by touching phone • Pay NOT explicit • recorded automatically when car pulls in and leaves. Does this happen anywhere? • ?

  11. Voting machines • Was move to optical scanner from lever machines good? • Positive features? • Negative features? • Why not online at site or not at site?

  12. Internet of Things • Evolving set of protocols for connecting devices over Internet or other networks • See http://embedded-computing.com/articles/internet-things-requirements-protocols/ • Responsiveness, scalability, robustness, etc. extra requirements over [merely] connecting computers and other mobile devices

  13. [More] Applications • Military • Medical • Other • May assume users are trained!

  14. Computer information system • Old definition, but still has value • CIS includes • Hardware • Software • People • Procedures

  15. Documentation • 1-pager • SUMMARY: what were you studying? What were the tasks (or some of the tasks)? Who were the subjects? What was the most important/surprising/anticipated findings? • PROOFREAD • Photograph(s) of interface, environment (if important) • Presentation: more details, but still “major on the majors”. • Details then analysis and summary

  16. Analysis • Consider & Talk about • Usability definition(s) • Effectiveness, efficiency, satisfaction • Cognitive load • Networking effects • Error prevention and recovery • Timing • Interactions of people and [intended] procedure with hardware and software • More

  17. Classwork • What are your plans? What is your approach?

More Related