Series 40 UI design for monetization enablers webinar - companion article - Revision history

Hamishwillee: Hamishwillee - Fix categories

2013-01-14T00:35:43Z

Hamishwillee - Fix categories

Hamishwillee: Hamishwillee -

2012-12-11T03:55:05Z

Hamishwillee -

Hamishwillee: Hamishwillee - Add SeeAlso links to other related articles

2012-12-11T03:52:29Z

Hamishwillee - Add SeeAlso links to other related articles

Kiran10182: Kiran10182 - FA template added

2012-12-02T13:53:03Z

Kiran10182 - FA template added

Krebbix: Krebbix - /* Introduction */

2012-11-22T08:28:09Z

Krebbix - - Introduction

Hamishwillee: Hamishwillee - /* Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? */ - tidy the Which problems occur if yo ... section

2012-11-21T23:51:36Z

Hamishwillee - - Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)?: - tidy the Which problems occur if yo ... section

Hamishwillee: Hamishwillee - Fix a few typos

2012-11-21T23:40:58Z

Hamishwillee - Fix a few typos

Krebbix: Krebbix - /* What is wrong with this layout? */

2012-11-21T13:08:35Z

Krebbix - - What is wrong with this layout?

Krebbix: Krebbix - /* Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? */

2012-11-21T12:54:31Z

Krebbix - - Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)?

Krebbix: Krebbix - /* Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? */

2012-11-21T12:49:24Z

Krebbix - - Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)?

@@ Line 1: / Line 1: @@
-[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]][[Category:In-App Advertising]][[Category:In-App Purchasing]]
+[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]][[Category:In-App Advertising]][[Category:In-App Purchasing]][[Category:Webinar]]
 {{FeaturedArticle|timestamp=20121202}}
 {{Abstract|This article is companion for the ''UI design for monetisation enablers for Series 40 Full Touch'' webinars held in November 2012. It covers both sessions: 13<sup>th</sup>  and 14<sup>th</sup> November 2012.}}

@@ Line 3: / Line 3: @@
 {{Abstract|This article is companion for the ''UI design for monetisation enablers for Series 40 Full Touch'' webinars held in November 2012. It covers both sessions: 13<sup>th</sup>  and 14<sup>th</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 2: / Line 2: @@
 {{FeaturedArticle|timestamp=20121202}}
 {{Abstract|This article is companion for the ''UI design for monetisation enablers for Series 40 Full Touch'' webinars held in November 2012. It covers both sessions: 13<sup>th</sup>  and 14<sup>th</sup> November 2012.}}
+{{SeeAlso|
 {{ArticleMetaData <!-- v1.2 -->
 |sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->

← Older revision		Revision as of 13:53, 2 December 2012
Line 1:		Line 1:
	[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]][[Category:In-App Advertising]][[Category:In-App Purchasing]]		[[Category:User Experience]][[Category:Series 40]][[Category:Touch UI]][[Category:Mobile Design]][[Category:Mobile Design Patterns]][[Category:Event]][[Category:In-App Advertising]][[Category:In-App Purchasing]]
		+	{{FeaturedArticle\|timestamp=20121202}}
	{{Abstract\|This article is companion for the ''UI design for monetisation enablers for Series 40 Full Touch'' webinars held in November 2012. It covers both sessions: 13<sup>th</sup> and 14<sup>th</sup> November 2012.}}		{{Abstract\|This article is companion for the ''UI design for monetisation enablers for Series 40 Full Touch'' webinars held in November 2012. It covers both sessions: 13<sup>th</sup> and 14<sup>th</sup> November 2012.}}

@@ Line 37: / Line 37: @@
 * Future UX webinars
 * [http://www.slideshare.net/nokia-developer/ui-design-for-monetisation-enablers-for-series-40-full-touch Slide deck]
-* Link to recording (to be added).
+* [http://forumnokia.adobeconnect.com/p6nb1gr5ztg/ Recording]
 * [http://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml Webinar announcement]
 ==  Proposals and solutions to webinar problems ==

@@ Line 78: / Line 78: @@
 === Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? ===
 {| class="wikitable"
 |-
-| [[File:S40UI monetization 06.png]] || [[File:S40UI monetization 07.png]] || [[File:S40UI monetization 08.png]]
+| [[File:S40UI monetization 07.png|frame|none|The ad is part of the "bottom" chrome and does not move anywhere.]] || [[File:S40UI monetization 08.png|frame|none|The category bar with an advertisement placed next to it. ]]
 |-
-| The ad is next to the header and could be either part of the chrome or part of the list (and scroll away with it) || The ad is chrome and does not move anywhere, but now it is partially hidden by the back button, which is not a good solution since
 * you might get false clicks with this solution by trying to push the back button
 * the ad is partially hidden, something what is not desired by the ad provider or the company paying for the ad
-|| The category bar with an advertisement placed next to it. The first problem with this approach is that the category bar will disappear as soon as you drill down (resulting in something like the 2nd image). Secondly, the area available for content is reduced significantly.
+|| The first problem with this approach is that the category bar will disappear as soon as you drill down (resulting in something like the 2nd image). Secondly, the area available for content is reduced significantly.
 |}
-* As you can see, the bottom of the view is not really suitable for ad placement on Series 40 full touch.
+We highly recommended you position the ad as part of the "top" platform chrome as shown in the following image. The benefits of having as part of the chrome is that it doesn't change position when you scroll away or drill down a level. In addition, it doesn't interfere with the Back button as shown in the previous examples.
-* In case you use the platform chrome and you want to make the ad being part of the chrome (i.e. not scroll away) the position as shown in the left example is highly recommended.
-** The ad does not change the position (e.g. when removing the Category in the next lower drill down level).
+[[File:S40UI monetization 06.png|frame|none|The ad is next to the header and could be either part of the chrome or part of the list (and scroll away with it)]]
-** The ad does not interfere with the Back button (in case there is no category bar).
 === What is wrong with this purchase flow? ===

@@ Line 64: / Line 64: @@
 Layout to be updated:
-* People with existing accounts or existing subscription will run into trouble with the this layout.
+* People with an existing account or subscription may run into trouble with this layout.
 * Users (also existing subscribers) tend to click the upper button automatically and wonder why they have to pay again.
@@ Line 87: / Line 87: @@
 * the ad is partially hidden, something what is not desired by the ad provider or the company paying for the ad
-|| The category bar with an advertisement placed next to it. The first problem with this approach is that the category bar will disappear as soon as you drill down (resulting in something like the 2nd image). Secondly, the area available for content is reduced signification.
+|| The category bar with an advertisement placed next to it. The first problem with this approach is that the category bar will disappear as soon as you drill down (resulting in something like the 2nd image). Secondly, the area available for content is reduced significantly.
 |}
@@ Line 114: / Line 114: @@
 * The short form allows people to get all information from the checkout form without scrolling.
 * The "place order" button is above the fold and immediately visible to the user.
-* Especially for returning customers it is faster to proceed, once all the fields are filled.
+* Once all the fields are filled this is much easier/faster to use. So this forum is particularly good for returning customers.
 |}

@@ Line 75: / Line 75: @@
 |}
-<!--
+For more examples and information on how design impacts sales and how to fix app designs, please visit [http://www.useit.com/ Jacob Nielsen's blog] and the [http://www.useit.com/alertbox/mobile-startup-screen.html WSJ mobile app example].
-Layout to be updated:
-−
-−
-−
-This is a simple example of how a bad or thoughtless design can screw up everything. There is a [ very nice example] found from [http://www.useit.com/ Jacob Nielsen's www.useit.com]. -->
 === Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? ===