Molde University College INF 245 Fall 2007 OBø Mobile Application Usability INF245 Mobile Applications Ola Bø.

Slides:



Advertisements
Similar presentations
DEVELOPING A METHODOLOGY FOR MS3305 CW2 Some guidance.
Advertisements

Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Chapter 11 Designing the User Interface
Usability and Performance Rules of Thumb for Mobile Java Developers Jackson Feijó Filho Software Developer Lightning talk at Java Mobile, Media & Embedded.
Microsoft Office 2007-Illustrated Introductory, Windows Vista Edition Windows XP Unit A.
User Interface Structure Design
Microsoft Office XP Microsoft Excel
DBSYSTEMS 1 of 23 Chapter 6 DB System Development: Forms and Reports 1 Based on G. Post, DBMS: Designing & Building Business Applications University of.
V0.1 Inclusive and Accessible Application Design June 21, 2012.
11 HCI - Lesson 5.1 Heuristic Inspection (Nielsen’s Heuristics) Prof. Garzotto.
Interaction Styles Course 6, CMC, 07/10/03 Direct Manipulation
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Multimedia Design Guidelines General Guidelines for Multimedia Learning Design.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
User Interface Design: Methods of Interaction. Accepted design principles Interface design needs to consider the following issues: 1. Visual clarity 2.
User Interfaces at Princeton By Ryan Walsh ’06 PSY 322 Spring 2004.
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 14 Designing.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Principles and Methods
McInterface User Interface Development Project IS 213 Spring 2001 Linda Harjono Saifon Obromsook John Yiu Wai Chi 1 st May, 2001.
© 2005 by Prentice Hall Chapter 3c Designing Interfaces and Dialogues.
Chapter 12 Designing Interfaces and Dialogues
GAO YUAN We are here for:  We know iPhone from iOS Human Interface Guidelines  The guidelines and principles that help you.
TrendReader Standard 2 This generation of TrendReader Standard software utilizes the more familiar Windows format (“tree”) views of functions and file.
Systems Analysis and Design in a Changing World, 6th Edition
WEBINAR SERIES: ACCESSIBLE INTERACTIVE DOCUMENTS Week 3: Accessible Web Forms Norman Coombs
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
Josh Probert – Yankee A Prototype based on Sierra’s SRS.
Systems Analysis and Design in a Changing World, 6th Edition
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
CS 4720 Usability and Accessibility CS 4720 – Web & Mobile Systems.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
©RavichandranUser interface Slide 1 User interface design.
Nielsen’s Ten Usability Heuristics
Usability Evaluation/LP Usability: how to judge it.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
10 Usability Heuristics for User Interface Design.
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
Sylnovie Merchant, Ph.D. MIS 161 Spring 2005 MIS 161 Systems Development Life Cycle II Lecture 3: Remember Prototyping? Data Storage Interface Design.
Designing Interface Components. Components Navigation components - the user uses these components to give instructions. Input – Components that are used.
1 Chapter 15 User Interface Design. 2 Interface Design Easy to use? Easy to understand? Easy to learn?
Productivity Programs Common Features and Commands.
William H. Bowers – High Level Design Torres 16.
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
Slide 1 Chapter 11 User Interface Structure Design Chapter 11 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman.
Technical Paper Review Designing Usable Web Forms – Empirical Evaluation of Web Form Improvement Guidelines By Amit Kumar.
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
12.1 CSC 123 Systems Analysis & Design Part IV: The Essentials of Design Chapter 12 Designing Effective Input.
1 User Interface Design Components Chapter Key Definitions The navigation mechanism provides the way for users to tell the system what to do The.
Evaluating a UI Design Expert inspection methods Cognitive Walkthrough
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
Input Design Lecture 11 1 BTEC HNC Systems Support Castle College 2007/8.
LECTURE 18 16/11/15. MAKING THE INTERFACE CONSISTENT Consistency is one way to develop and reinforce the users conceptual model of applications and give.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Basic Elements.  Design is the process of collecting ideas, and aesthetically arranging and implementing them, guided by certain principles for a specific.
William H. Bowers – Specification Techniques Torres 17.
Printed Reports Analysis questions –Who will use the report? –What is the purpose of the report? –When or how often is the report needed? –Where does the.
© 2016 Cognizant. © 2016 Cognizant Introduction PREREQUISITES SCOPE Heuristic evaluation is a discount usability engineering method for quick, cheap,
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Ten Usability Heuristics These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of.
User Interface Design Chapter 10.
Chapter 2 Hix & Hartson Guidelines.
Chapter 14 Designing Interfaces and Dialogues
Database Applications – Microsoft Access
A NEW FACE OF THE TECHNICAL COMMUNICATOR – UX IS OUR STRENGTH – WE DESIGN TO WRITE BY CHRIS GANTA © 2016, STC INDIA CHAPTER.
One-timer?. A new face of the technical communicator – UX is our strength – we design to write.
Systems Analysis and Design in a Changing World, 6th Edition
Presentation transcript:

Molde University College INF 245 Fall 2007 OBø Mobile Application Usability INF245 Mobile Applications Ola Bø

Molde University College INF 245 Fall 2007 OBø Based on Series 60 Developer, Platform 2.0: Usability Guidelines for Enterprise Applications (Nokia)

Molde University College INF 245 Fall 2007 OBø Usability Depends on many factors in addition to the product Usability is the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use ISO (1998)

Molde University College INF 245 Fall 2007 OBø Three principles for designing usable applications 1. Know the user and the context. Then you can prioritize functionality and user dialog 2. Test with real users – early and several taimes 3. Choose simplicity.

Molde University College INF 245 Fall 2007 OBø What do we gain by improving usability? Effects obtained by pursuing usability Some usability improvements are easy to obtain -dropped functionality -changed terminology

Molde University College INF 245 Fall 2007 OBø Usability in application development Traditional system development Starts by specifying requirements in cooperation with the users The users will not see the system before it is completed When the system is completed it is too late to make changes Results in most cases in a product with low usability

Molde University College INF 245 Fall 2007 OBø Involving the users and other stakeholders. By consulting the users several times in the development process and adjusting requirements a better product can be made Early involvment using paper prototyping Several personell categories participate

Molde University College INF 245 Fall 2007 OBø Checklists Usability can also be improved using checklists

Molde University College INF 245 Fall 2007 OBø Main problem for mobile applications: Too much time is used for navigations Each screen must show: 1. Where am I 2. Where can I go from here Means for navigation Navigation key Soft keys Short-cut keys Guidelines 1 Navigation Consistency is important to support learning both inside and between applications Use navigation solutions the users already know Show soft key labels Follow the standard for use of soft-keys Use standard terminology in users own language Use automatic storage and retrieval Inconsistent soft key labels is the often the main usability problem

Molde University College INF 245 Fall 2007 OBø Guidelines 2 The Main Menu Core functionality should be easily accessible Different menu solutions are used in existing applications Menu only using soft key Usable for simple applications Custom menus pros and cons?

Molde University College INF 245 Fall 2007 OBø Alternative menus Menu on screen Submeny on soft key Simple applications Meny on tabs and on soft keys More complex applications Some users do not perceive the tabs Tab

Molde University College INF 245 Fall 2007 OBø Alternative menus Second level tabs Major applications with much information Icons should only be used if their meaning is obvious !?? What is available using the navigation key should also be available using the menus

Molde University College INF 245 Fall 2007 OBø Option menus Use consistent terms Most used functionality first Why? What functionality is most used Logical order Group related choices into sub menus Avoid scrolling in sub menus Only show available choices Why?

Molde University College INF 245 Fall 2007 OBø Action Feedback should always be given Should react within 0,1s If the action takes more time: 0,5-2 s tell user something is happening More than 2 s: indicate how much time remains to complete the operation using a progress indicator

Molde University College INF 245 Fall 2007 OBø Information input As little as possible, as simple as possible How do you obtain this? A good default value Only necessary input Reduced quantity Abbreviations Cut and paste Selection better than writing, also speaking is. Changing numerical input using navigation key Formatting help Sound and picture is an alternative Respect the users’ work

Molde University College INF 245 Fall 2007 OBø Information Output Chunking and order Text presentation Fonts and contrast Graphics Visibility Icons Color Consistency Sound Never solely Volume control and stop Errors Prevention and tolerance Undo Confirmation NB! different keys Help Options-menu Context sensitive

Molde University College INF 245 Fall 2007 OBø Communication with servers Coverage problem handling The application should be robust in case of lost connection What does that mean? Synchronization handling automatic vs. manual legal liability? Use of words End, Close, shut down, Start, Open, Log in Where are the possible misunderstandings here? Status indication – Result indication

Molde University College INF 245 Fall 2007 OBø Security and usability Why may security and usability be conflicting? How to ensure Safer log on Less frequent log on Less handling of sensitive information Safer handling of sensitive information

Molde University College INF 245 Fall 2007 OBø Exercise