Series 40 UI design for monetization enablers webinar - companion article
m (Krebbix - - →Open issues from Q/A) |
hamishwillee
(Talk | contribs) m (Hamishwillee - Subedit) |
||
| Line 27: | Line 27: | ||
== Introduction == | == Introduction == | ||
| − | 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 | + | 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 receive follow-up treatment in a (this!) Nokia Developer Wiki article. |
The webinar and the wiki article are a great starting point if you’re not a UI design expert. Check out [https://www.developer.nokia.com/Resources/Library/Full_Touch/#!index.html Series 40 UI design library] for more advanced information and resources. | The webinar and the wiki article are a great starting point if you’re not a UI design expert. Check out [https://www.developer.nokia.com/Resources/Library/Full_Touch/#!index.html Series 40 UI design library] for more advanced information and resources. | ||
| Line 39: | Line 39: | ||
* Link to recording (to be added). | * Link to recording (to be added). | ||
* [http://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml Webinar announcement] | * [http://www.developer.nokia.com/Resources/Multimedia/Webinars.xhtml Webinar announcement] | ||
| + | |||
== Proposals and solutions to webinar problems == | == Proposals and solutions to webinar problems == | ||
| − | This section contains problems raised in the webinar exercises. | + | This section contains problems raised in the webinar exercises. In addition, it contains proposals and possible solutions to solve the problems. |
=== Where would you place “buy more levels” button(s) in a game? === | === Where would you place “buy more levels” button(s) in a game? === | ||
| Line 50: | Line 51: | ||
* Level selection page | * Level selection page | ||
* Score overview | * Score overview | ||
| − | * | + | * It could be present on all menus |
| − | + | ||
| + | |||
| + | Also, a link for visiting your web page should minimally be part of all options menus (for example, in order to promote new games or sequels to this game). | ||
=== What is wrong with this layout? === | === What is wrong with this layout? === | ||
| Line 68: | Line 70: | ||
Proposal: | Proposal: | ||
| − | * This layout layout | + | * This layout layout presents and explains both options with equal weight; this way it is much less likely that the user select the wrong button "automatically". |
| − | * | + | * The wording has changed from subscribe to register, and what is meant by registration has been explained clearly in the text. Registration is a better choice because it implies something that you do once to access a service across multiple devices, while subscription may be interpreted as something you need to do for every device. |
|} | |} | ||
| + | <!-- | ||
Layout to be updated: | 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 Jacob Nielsen's | + | 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)? === | === Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)? === | ||
| Line 85: | Line 88: | ||
| [[File:S40UI monetization 06.png]] || [[File:S40UI monetization 07.png]] || [[File:S40UI monetization 08.png]] | | [[File:S40UI monetization 06.png]] || [[File:S40UI monetization 07.png]] || [[File:S40UI monetization 08.png]] | ||
|- | |- | ||
| − | | The ad is next to the header and could be either part of the chrome or | + | | 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 | * you might get false clicks with this solution by trying to push the back button | ||
| − | * the ad is partially hidden, something what is not | + | * the ad is partially hidden, something what is not desired by the ad provider or the company paying for the ad |
| − | || The category bar | + | || 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. |
|} | |} | ||
| − | As you can see, the bottom | + | As you can see, the bottom of the view is not really suitable for ad placement on Series 40 full touch. |
| − | + | ||
| + | === What is wrong with this purchase flow? === | ||
| + | Note, this assumes you are already signed-in to Nokia Store. | ||
| − | + | [[File:S40UI monetization 02.png|none]] | |
| − | [[File:S40UI monetization 02.png]] | + | |
* The flow does not tell the total costs, but rather tries to trick the user with a low price per unit. | * The flow does not tell the total costs, but rather tries to trick the user with a low price per unit. | ||
* People would expect that you charge them daily - which does not hurt that much than paying over 100€ at once. | * People would expect that you charge them daily - which does not hurt that much than paying over 100€ at once. | ||
| − | * The flow shown above is very likely to cause complaints and bad ratings in the store | + | * The flow shown above is very likely to cause complaints and bad ratings in the store. Users may even want to return the app since they feel they are being cheated. |
| Line 111: | Line 114: | ||
|- | |- | ||
| [[File:S40UI monetization 03.png]] || [[File:S40UI monetization 04.png]] || Usually the left example is preferred, since: | | [[File:S40UI monetization 03.png]] || [[File:S40UI monetization 04.png]] || Usually the left example is preferred, since: | ||
| − | * The short checkout form assumes that you change nothing or very little | + | * The short checkout form assumes that you change nothing or very little once it is filled it (data may also be retrieved from a service). This also allows you to combine information into related fields (e.g. credit card company and credit card number). |
| − | * The short form | + | * 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. | * 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. | * Especially for returning customers it is faster to proceed, once all the fields are filled. | ||
Revision as of 05:46, 21 November 2012
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: 13th and 14th November 2012.
Article Metadata
Contents |
Introduction
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 receive follow-up treatment in a (this!) Nokia Developer Wiki article.
The webinar and the wiki article are a great starting point if you’re not a UI design expert. Check out Series 40 UI design library for more advanced information and resources.
This wiki page is the "companion" to the webinar. It includes:
- Webinar exercises and proposals for how to solve them.
- Open issues from Q/A
- Further links and references
- Future UX webinars
- Slide deck
- Link to recording (to be added).
- Webinar announcement
Proposals and solutions to webinar problems
This section contains problems raised in the webinar exercises. In addition, it contains proposals and possible solutions to solve the problems.
Where would you place “buy more levels” button(s) in a game?
Place the "buy more levels" here:
- Landing page (after the splash screen)
- Level selection page
- Score overview
- It could be present on all menus
Also, a link for visiting your web page should minimally be part of all options menus (for example, in order to promote new games or sequels to this game).
What is wrong with this layout?
| Layout to be updated | Proposal | Decription |
|---|---|---|
 |
 |
Layout to be updated:
|
Which problems occur if you place the ad at the bottom of the view (in series 40 Full Touch)?
 |
 |
|
| 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
|
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. |
As you can see, the bottom of the view is not really suitable for ad placement on Series 40 full touch.
What is wrong with this purchase flow?
Note, this assumes you are already signed-in to Nokia Store.
- The flow does not tell the total costs, but rather tries to trick the user with a low price per unit.
- People would expect that you charge them daily - which does not hurt that much than paying over 100€ at once.
- The flow shown above is very likely to cause complaints and bad ratings in the store. Users may even want to return the app since they feel they are being cheated.
Which checkout concept do you prefer and why?
| Short checkout form with drill down | Long form | Description |
|---|---|---|
 |
 |
Usually the left example is preferred, since:
|
Open issues from Q/A
Question: About the IAP, what if user has same account for 2 phones?
Answer: The re-downloads are not locked to an IMEI. They are based on the account. So the user could upload to 10 different devices as long as that content supports those devices.
Thanks Sherwin :-)
Further links and references
- In-app advertising
- In-app purchase
- Battle Tank (Nokia DRM demo app)
- Tourist Attraction (Custom DRM demo app)
- UI Components Demos App
- Functional description of in-app purchase
- Jacob Nielsen’s show case “Why WSJ Mobile App Gets ** Customer Reviews”.
- Mobile Design Pattern Gallery: UI Patterns for Mobile Applications. Theresa Neil (2012). ISBN-13: 978-1449314323
- Designing Mobile Interfaces. Steven Hoober, Eric Berkman (2011). ISBN-13: 978-1449394639
Future webinars
The next (planned) UX related webinar is: Debug your design for Series 40 full touch.
It is important to test your application, not only code wise but also from UX point of view. The webinar will show you very simple and “one-man-band” compatible test methods to find UX bugs and how to deal with them. As usual, this UX webinar will have a wiki companion article for the exercises.
