Series 40 UX checklist webinar - companion article - Revision history

Hamishwillee: Hamishwillee - Fix categories

2013-01-14T00:33:26Z

Hamishwillee - Fix categories

Kiran10182: Kiran10182 - FA template added

2012-12-17T09:45:53Z

Kiran10182 - FA template added

Hamishwillee: Hamishwillee -

2012-12-11T03:54:57Z

Hamishwillee -

Hamishwillee: Hamishwillee - Add SeeAlso links to other related articles

2012-12-11T03:52:18Z

Hamishwillee - Add SeeAlso links to other related articles

Hamishwillee: Hamishwillee - Minor subedit for readability

2012-11-13T00:15:21Z

Hamishwillee - Minor subedit for readability

Krebbix: Krebbix - /* A custom view acts as a launchpad screen. Which chrome elements do you add? */

2012-11-12T06:55:22Z

Krebbix - - A custom view acts as a launchpad screen. Which chrome elements do you add?

Krebbix: Krebbix - /* A custom view acts as a launchpad screen. Which chrome elements do you add? */

2012-11-12T06:54:14Z

Krebbix - - A custom view acts as a launchpad screen. Which chrome elements do you add?

Krebbix: Krebbix - /* Is the contrast of these two colors good enough for AAA compliance for text? */

2012-11-12T06:51:23Z

Krebbix - - Is the contrast of these two colors good enough for AAA compliance for text?

Hamishwillee: Hamishwillee - Minor subedit

2012-11-06T04:37:17Z

Hamishwillee - Minor subedit

Krebbix: Krebbix - /* Future webinars */

2012-11-05T08:55:58Z

Krebbix - - Future webinars

@@ Line 1: / Line 1: @@
-[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]]
+[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Webinar]]
 {{FeaturedArticle|timestamp=20121216}}
 {{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}

@@ Line 1: / Line 1: @@
 [[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]]
 {{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}
 {{SeeAlso|

@@ Line 2: / Line 2: @@
 {{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}
 {{SeeAlso|
-* [[Series 40 UI design usabillity testing webinar - companion article]]
+* [[Series 40 UI design usability testing webinar - companion article]]
 * [[Series 40 UI concept design webinar – companion article]]
 * [[Series 40 UI game design tips webinar – companion article]]

@@ Line 1: / Line 1: @@
 [[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]]
 {{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}
+{{SeeAlso|
 {{ArticleMetaData <!-- v1.2 -->
 |sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->

@@ Line 44: / Line 44: @@
 === A custom view acts as a launchpad screen. Which chrome elements do you add? ===
-(Chrome could also be referred as screen furniture. It is fixed to the upper and/or lower edge of the screen and it contains important navigation functions, system indicators and view titles. Chrome does not scroll away.)
+The Chrome, or "screen furniture" is the framework-provided notification area containing system indicators, view titles and other important navigation information. It is fixed to the upper and/or lower edge of the screen and does not scroll away. Different chrome elements are appropriate depending on your use case.
 There are several possibilities:
@@ Line 89: / Line 89: @@
 * Background: AAFF33
-AAA compliance means that you create a document in a way that also disabled people can access it. Even if not stated directly, it also means that your document (or application) can be accessed by non-disabled persons in a non-optimum environment, e.g. with sunlight shining directly to the display. [http://www.w3.org/TR/WAI-WEBCONTENT/ More information from here.]
+A document is AAA compliant if it can be used by people who are visually impaired. Though not stated directly, AAA compliance also means that your document (or application) can be accessed more effectively by non-disabled users in a non-optimum environment, e.g. with sunlight shining directly on the display. More information can be obtained [http://www.w3.org/TR/WAI-WEBCONTENT/ here].
-If you fill the values to a contrast checker, the answer is "No". The colour contrast results in something like the image below:
+After testing the values in a contrast checker, we see that the answer is "No". The colour contrast results in something like the image below:
 [[File:S40UI_checklist_03.png|none]]

@@ Line 1: / Line 1: @@
 [[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]]
-{{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars to be held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}
+{{Abstract|This article is companion for the ''UX Checklist for Series 40 Full Touch'' webinars held in October and November 2012. It covers both sessions: 31<sup>st</sup> October 2012 and 1<sup>st</sup> November 2012.}}
 {{ArticleMetaData <!-- v1.2 -->
@@ Line 44: / Line 44: @@
 === A custom view acts as a launchpad screen. Which chrome elements do you add? ===
 There are several possibilities:
-# Full custom header without chrome: there is no chance to add neither any primary command nor any options menu. This could work in case the launch-pad view is just putting the user into the right flow, e.g. for a game:
+# Full custom header without chrome: there is no chance to add neither any primary command nor any options menu. This could work in case the launch-pad view just puts the user into the right flow, e.g. for a game:
 #* Start new single player game
 #* Start new multiple player game
@@ Line 52: / Line 52: @@
 #* Help
 #* About
-# Full custom header with one primary action: This works in case there is one first very important action, which the user is usually doing before continuing with any other action or which has to be always available, e.g. the play/pause button of a music player. The launch-pad view allows the user to continue directly with the main use cases.
+# Full custom header with one primary action: This works if there is a single very important action which the user will most often select, or which always has to be available, e.g. the play/pause button of a music player. The launch-pad view allows the user to continue directly with the main use cases.
-# A view with predefined chrome, or chrome at the predefined position, it becomes now easy to clean up the launch pad from secondary items, i.e. Help and about might be moved to the Options menu. <br />
+# A view with predefined chrome, or chrome at the predefined position. This approach makes it easy to remove secondary items from the launchpad: i.e. Help and about might be moved to the Options menu.
 [[File:S40UI_checklist_01.png]]
 === How do you open the item menu and what do you place in there? ===
-The item menu is opened with long press on the item. It contains only commands which directly affect only to the selected item (e.g. delete). It does not contain any commands which could act on multiple items (e.g. delete all). The latter go to the view menu. These are the design rationales for touch devices:
+The item menu is opened with long press on the item. It must contain only commands which directly the selected item (e.g. delete). It must not contain any commands which could act on multiple items (e.g. delete all). The latter go to the view menu. These are the design rationales for touch devices:
 * The focus is implied with the touch down, but not beforehand, so the phone cannot anticipate which item is chosen
 * The focus is lost with finger lift, so the phone cannot trace which item was chosen beforehand
-* There are just few working interaction pattern which would resolve these issues,
+* There are just few working interaction pattern which would resolve these issues:
 ** pointing at the item for longer time (all Nokia touch phones)
 ** bringing the phone into a selection mode and from there select the item (e.g. Android 4.0 and higher)
 === How many touchable items can you fit into a full screen layout? ===
-* 4 items in one row in case you obey the minimum touch area. The 5th item does not fully anymore and it might interfere with the scroll bar (which is without function and just for indication purposes). However, it is not recommended to go below 7 mm x 7 mm touch area and 1mm margin. To fill the gaps, rather increase the touch area than squeezing in another item.
+* 4 items fit in one row if you use the minimum touch area. A 5th item will not fit completely and might interfere with the scroll bar (which is without function and just for indication purposes). We recommend you do not reduce the touch area below 7 mm x 7 mm and 1mm margin. If you need to fill the gaps, increase the touch area in preference to squeezing in another item.
 * 7 items in a column are fully visible and 1 item is partially visible
 * 28 full items
 * 32 items the user is aware of
-In case of a 5th column, take the back button into account, i.e. 40 – 1 items. However, in that case make sure the context of use allows smaller touch areas (e.g. no thumb use, i.e. the user will operate the phone always with 2 hands) or cover-up with certain techniques, e.g. fish-eye.<br />
+If using a 5th column, take the back button into account (i.e. 40 – 1 items). In this case make sure the context of use allows smaller touch areas (i.e. the user will always operate the app with 2 hands so thumb use is not required) or compensate using techniques like fish-eye.
 [[File:S40UI_checklist_02.png]]
@@ Line 79: / Line 78: @@
 === Which icon sizes are used in Series 40 full touch? ===
-[https://www.developer.nokia.com/Resources/Library/Full_Touch/#!ux-checklist.html Please check from here.]
+[https://www.developer.nokia.com/Resources/Library/Full_Touch/#!ux-checklist.html See answer here].
@@ Line 87: / Line 86: @@
 * Background: AAFF33
-No.<br />
+No. The colour contrast results in something like the image below:
-[http://snook.ca/technical/colour_contrast/colour.html Please check from here.]<br />
+[[File:S40UI_checklist_03.png|none]]
-Fill the values . Those will result in something like the following image.<br />
-[[File:S40UI_checklist_03.png]]
+You can check colour contrasts using sites like [http://snook.ca/technical/colour_contrast/colour.html snook.ca]
@@ Line 101: / Line 99: @@
 == Future webinars ==
-The next (planned) UX related webinar is:<br />
+The next (planned) UX related webinar is: '''UI design for monetisation enablers for Series 40 full touch.'''
-'''UI design for monetisation enablers for Series 40 full touch.''' <br />
-How you design and present monetisation interactions requires as much attention to user experience as does the rest of your app. If you use in-app ads or in-app purchasing, this UX webinar is for you. The webinar will walk you through the recommended flows of various monetisation stories in Series 40 full touch. It will also demonstrate common mistakes that developers make and will propose solutions for those problems. As usual for Nokia Developer UX webinars, the presentation will feature exercises that will receive follow-up treatment in a Nokia Developer Wiki article.<br />
+How you design and present monetisation interactions requires as much attention to user experience as does the rest of your app. If you use in-app ads or in-app purchasing, this UX webinar is for you. The webinar will walk you through the recommended flows of various monetisation stories in Series 40 full touch. It will also demonstrate common mistakes that developers make and will propose solutions for those problems. As usual for Nokia Developer UX webinars, the presentation will feature exercises that will receive follow-up treatment in a Nokia Developer Wiki article.
 * 13.11.2012, 10:00 Helsinki time, [https://events-emea1.adobeconnect.com/content/connect/c1/799911421/en/events/event/shared/default_template_simple/event_landing.html?sco-id=1098045550&_charset_=utf-8 register]
@@ Line 109: / Line 107: @@
+[https://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml Find more webinar announcements from this link]
-[https://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml You find more webinar announcements from here.]