The document summarizes a lecture on UI design for Nokia S60 devices. Part I discusses drafting a concept for a mobile device for users on the move, focusing on maps, music, weather, calendar and call functions for young professionals using their phone in cars. Part II discusses the process of taking a design from concept to final product, including considerations of components, branding, readability, usability testing and communication between internal teams and vendors.

1. A Review on the Lecture Given by Juha-Matti UI Design in Nokia S60 Structure: Part Ⅰ: Drafting an “On the Move” concept ● how to get down to basic Part Ⅱ: Design case study E71 theme ● how to get into the final product

2. Part Ⅰ : Device on the Move Step one: set the target: device on the move Step two: start with study on who, where and what look at the category below: original thinking what: maps, music, weather, calendar, info, call where: who: young aged professional car Sunday exercise cycling jogger tourist walking pedestrian

3. Step three: cutting the impossible after 1st iteration round what: maps, music, weather, calendar, info, call where: who: after 2nd iteration round what: maps, music, weather, calendar, info, call where: who: focus on the car mode the aged was skipped but still too many apps young aged professional car young professional car

4. conclusion the ever rotating process of “ communicate-iterate-communicate-iterate… ” idea group discussing improve scenarios/ personas improve flash

5. Part Ⅱ : Road to Final Products components and functions category differentiation Nokia level brand identity design readability message of device family customer vendors in-house implementation SW (scalability, work) usability testing money communication (theme) vendor available components restriction platform

6. design versus design patterned background 3D-like highlights special color business main view readability subdued colors (supporting) usability category differentiation Nokia level brand identity design readability message of device family customer

7. ○ local: face to face communication ○ access to databases ○ same processes ○ remote: e-mail communication ○ restricted access to databases ○ no common processes vendors in-house implementation

8. solve the problem in communication between different components image for common understanding: use images to make clear each responsibility

9. conclusion communication ○ KISS: keep it simple and stupid ○ never assume that the receiver of your message thinks as you do SW- graphic designer- new/old employee ○ make sure that your point of view is clear to all and make sure you understand theirs too ○ always ask a second opinion by Jacqueline