Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.
Series 40 UI design port from Android webinar - companion article
This article is companion for the UI design techniques for porting Android apps to Series 40 full touch webinars held in October 2012. It covers both sessions: 4 October 2012 and 10 October 2012.
- Series 40 UI design usabillity testing webinar - companion article
- Series 40 UI concept design webinar – companion article
- Series 40 UI game design tips webinar – companion article
- Series 40 UI design port from Android webinar - companion article
- Series 40 UX checklist webinar - companion article
- Series 40 UI design for monetization enablers webinar - companion article
Porting an application design from Android to Series 40 is not as difficult as it might first appear. While Series 40 phones are cost-optimized, their smartphone-like experience is provided by a UI with many comparable features.
For the webinar examples we’re comparing designs for devices with similar sizes: Series 40 Full touch (3’’ screen) and e.g. Galaxy Mini (3,14’’ screen). Some of the advice may also apply to devices with larger sizes.
The webinar addresses basic UI design aspects when porting a design from Android "Jelly Bean" to Series 40 full touch. This wiki page is the "companion" to the webinar. It includes:
- Webinar exercises and proposals for how to solve them.
- Q/A from the webinar sessions
- Link to slide deck
- Link to recording
- Webinar announcement
- Register 4 October 2012 or 10 October 2012
This section contains problems raised in the webinar exercises along with recommended solutions (solutions will be added after the second session).
How would you change the following structure for Series 40 full touch?
One solution could be the following proposal:
How do Android Jelly Bean and Series 40 full touch differ in their use of the “select multiple items” pattern?
Android OS 4.0 and newer use the following steps:
- long press one item
- selection mode opens
- select item(s)
- press command (or open the overflow and press command from there)
Series 40 uses the following steps:
- Select action (either from action button #1 or from options menu)
- multi-selection lists opens
- select items
- confirm (usually by pressing the check-mark in action button #1)
Which device has more pixels, the Samsung Galaxy Mini S5570 or the Nokia Asha 311?
- Galaxy Mini S5570 with 240 x 320 pixels = 76800 px, 3,14
- Nokia Asha 311 with 240 x 400 pixels = 96000 px, 3
- Alerts can have 0 – 3 buttons. Position and layout are predefined.
- StringItem in a Form screen can be dressed as a button or as a labelled button. It is only possible to show one button per row.
- The CustomItem in Form screen can host a button or a button group.
- The full screen Canvas can contain buttons. The 4th image shows custom surround-shaped push-buttons with icons and with additional text below the push button. If the button is based on icons it is many times beneficial to add text explaining the action being mapped to the button.
- A Canvas with a custom toolbar, as shown in the 5th image. Do not place more than 5 items in a toolbar.
What are the benefits of Series 40 full touch backstep paradigm?
- It is not possible to show unknown screens to the user.
- Backstep contains only the previous views (but no parallel views, i.e. it does not jump between categories in the category bar).
- It is optimized for small screen, where the information has to be compact. Therefore the navigation must be as simple as possible.
- It is in line with previous Nokia backstep paradigms from other platforms like Symbian.
Q: Is Adobe air supported in Series 40?
Portions of this wiki page contains modifications or is reproduced based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.