WP 4.4: Interface/Interaction Guidelines Gregor Broll, Heinrich Hußmann University of Munich (LMU) Department for Computer Science, Media Informatics SMS Meeting, 3rd/4th December 2007 Herrsching, Germany

LMU, SMS Meeting, Herrsching, Germany, /11 Agenda Current status of development of interfaces/interaction patterns for SMS Integration with other WPs Deliverable Next steps

LMU, SMS Meeting, Herrsching, Germany, /11 Towards SMS Design Guidelines Development of design guidelines from: Functional requirements (WP4.1) SMS scenarios (e.g. interface mock-ups) Storyboarding, paper-prototyping, focus groups Agenda for finding interfaces/interaction patterns for SMS application: Survey of existing interface/interaction patterns Prototyping and evaluating different interfaces Implementation of a reference application based on evaluation results Further evaluation (e.g. against alternative approaches or focued on specific features) Development of guidelines Design Guidelines Functional Requirement Interfaces, Interaction Patterns, …

LMU, SMS Meeting, Herrsching, Germany, /11 Related Work and Analysis Survey of existing: (mobile) interface and interaction patterns/guidelines/libraries usability and design guidelines for mobile applications, e.g. from Nokia technologies, toolkits, etc. for the development of mobile interfaces, e.g. Java ME, Thinlets. What are the functional requirements for SMS-applications? What are additional standard-procedures, feedback mechanisms, menu structures, graphical design, etc. in SMS applications? What are existing guidelines/patterns for (mobile) interfaces/interactions? How can these be applied to the functional requirements from SMS? What are useful interfaces/interaction patterns for SMS features?

LMU, SMS Meeting, Herrsching, Germany, /11 Prototyping - Basics Paper-prototypes of different interfaces/interaction patterns Based on functional requirements Different alternative designs for different interfaces/interactions Apply whole range of investigated interfaces, interaction patterns and gui widgets Focus on: Key features of SMS: startscreen, What’s here, TakeMe2, services, MEM, SMS points Standard components: Login/logout, contacts, settings, filter, order, rating, feedback Basic layout: icons vs. text, grid/list/tab layout, map, menu structure, navigation

LMU, SMS Meeting, Herrsching, Germany, /11 Prototyping - Examples

LMU, SMS Meeting, Herrsching, Germany, /11 Evaluation Evaluation of different paper-prototypes in a meta-scenario Focus on a selection of interface/interaction features/issues: What‘s here Order and filter Wizard (using a service) Receiving and using a MEM TakeMe2 SMS point Navigation Startscreens Contacts Includes features from Lancaster proposal (e.g. service discovery, MEM) Expected results: Input for basic guidelines Basis for development of reference application

LMU, SMS Meeting, Herrsching, Germany, /11 Integration with WP4.1 and WP3 Different options for (further) evaluation and integration: 1.Combination of LMU and Lancaster proposals for planned evaluation -Takes too long -Current study already very big 2.Evaluation of LMU reference implementation, Lancaster design and MOVE +Refined evaluation - find out (dis)advantages of all 3 designs +Pick best features for SMS reference design -Takes quite some time -Redundant efforts (3 client implementations) 3.Application of evaluation results to MOVE client +Fast application of evaluation results +Refined MOVE client as reference application +More time to focus on development and evaluation of SMS specific features (e.g. MEM, SMS points, …) + WP4.1 and WP4.4 to provide alternative designs for evaluation => pick best designs

LMU, SMS Meeting, Herrsching, Germany, /11 Deliverable – Preliminary Outline Due at the end of January 2008 Overview of usability development process Preliminary study on future trends in mobile hard- and software Existing interface/interaction guidelines for mobile applications Technical prerequisites for implementing interfaces (Java ME, Thinlets, etc.) Analysis Functional requirements and application of existing guidelines/patterns Design of alternative mobile interfaces (paper-prototypes) Design of Lancaster proposal (?) User study and evaluation Preliminary guidelines (based on results of user study) Outlook Application of guidelines to MOVE client Further development and evaluation of SMS specific features

LMU, SMS Meeting, Herrsching, Germany, /11 Deliverable – Partner Contributions Sagem Orga: resumes work on interfaces for security and privacy All partners: Run the evaluation/user study with at least 5 people in their home countries Materials (study outline, questionnaire, etc.) will be provided Confirmed by: Sagem Orga, VTT, XiWrite, Radiolabs Deadline for all contributions: 11 th January 2008

LMU, SMS Meeting, Herrsching, Germany, /11 Summary / Next Steps User study, evaluation, definition of basic SMS design guidelines Application of these guidelines to the MOVE client Further, more detailed evaluation of selected SMS issues (e.g. MEMs, navigation, interaction with SMS points, …) => WP4.1 and WP4.4 Compare Java ME/Thinlet-interfaces against competition, e.g. HTML