×
Namespaces

Variants
Actions
(Difference between revisions)

Series 40 UI design port from Android webinar - companion article

From Nokia Developer Wiki
Jump to: navigation, search
Krebbix (Talk | contribs)
m (Krebbix -)
 
Krebbix (Talk | contribs)
m (Krebbix -)
Line 1: Line 1:
 
[[Category:Draft]]
 
[[Category:Draft]]
''Delete instructional text in italic''
+
'{{Abstract|This article is companion for the [[#Future webinars|UI design techniques for porting Android apps to Series 40 full touch]] held in October 2012. It covers both sessions (4 October 2012 and 10 October 2012)}}.
 
+
{{Abstract|This article explains how to ... }} ''Replace the abstract text with a short paragraph (or sentence) describing what the topic covers.''
+
 
+
''Enter article metadata as described below. Note that this template can be placed anywhere in the article. Do not remove parameters that you do not use''
+
 
{{ArticleMetaData <!-- v1.2 -->
 
{{ArticleMetaData <!-- v1.2 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 12: Line 8:
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->  
+
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
|signing=<!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
+
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|translated-by= <!-- [[User:XXXX]] -->
 
|translated-by= <!-- [[User:XXXX]] -->
|translated-from-title= <!-- Title only -->  
+
|translated-from-title= <!-- Title only -->
 
|translated-from-id= <!-- Id of translated revision -->
 
|translated-from-id= <!-- Id of translated revision -->
|review-by=<!-- After re-review: [[User:username]] -->
+
|review-by= <!-- After re-review: [[User:username]] -->
 
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 
|update-by= <!-- After significant update: [[User:username]]-->
 
|update-by= <!-- After significant update: [[User:username]]-->
 
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 
|update-timestamp= <!-- After significant update: YYYYMMDD -->
|creationdate= <!-- Format YYYYMMDD -->
+
|creationdate= 20121003
|author= <!-- Display as link [[User:username]] -->
+
|author= [[User:Krebbix]]
 
}}
 
}}
  
 
== Introduction ==
 
== Introduction ==
  
 +
Porting the application design from Android to Series 40 is not that difficult as it might look at first. Series 40 phones are cost-optimized phones, yet with smartphone alike experience.
 +
The webinar addresses basic UI design aspects when porting a design from Android Jelly Bean to Series 40 full touch. (However, you should compare the UI design from Android devices with small screens (e.g. 3.2'' phones) to Series 40 phones.) This is the companion wiki page.
  
 +
It includes:
 +
* Webinar exercises (will turn into "Recommended solutions problems raised by the webinar exercises" after the second webinar session)
 +
* Q/A from the webinar sessions
 +
* Link to slide deck [will be added].
 +
* Link to recording [will be added]
  
== Summary ==
+
{{Note|The information is related to Android OS 4.1 "Jelly Bean and Series 40 full touch.}}
 
+
+
''Remove Category:Draft when the page is complete or near complete''
+
 
+
 
+
''The "platform categories" will be displayed here in '''preview''' only - Copy paste relevant categories into text here''
+
  
{{VersionHint|Versions will be visible from this template when viewed in preview. You can delete this or leave it in the page as it is not displayed in final version}}
+
== Webinar problems ==
 +
This section contains problems raised in the webinar exercises. The recommended solutions will be added after the second session.
 +
# How would you change the following structure for S40FT?
 +
# How do Android Jelly Bean and Series 40 full touch differ from selecting multiple?
 +
# Which device has more pixels, the Samsung Galaxy Mini S5570 or the Nokia Asha 311?
 +
# Are there any limitations in using buttons in S40FT?
 +
# What are the benefits of S40FT backstep paradigm?
  
''Add categories below using category selector.''
+
==== Disclaimer ====
 +
Portions of this wiki page contains modifications or is reproduced based on work created and shared by the [http://code.google.com/policies.html Android Open Source Project] and used according to terms described in the [http://creativecommons.org/licenses/by/2.5/ Creative Commons 2.5 Attribution License].
 +
* [http://developer.android.com/index.html Android development]
 +
* [http://developer.android.com/design/index.html Android UI design]

Revision as of 11:52, 3 October 2012

'This article is companion for the UI design techniques for porting Android apps to Series 40 full touch held in October 2012. It covers both sessions (4 October 2012 and 10 October 2012).

Article Metadata
Compatibility
Platform(s):
Series 40
Article
Created: Krebbix (03 Oct 2012)
Last edited: Krebbix (03 Oct 2012)

Introduction

Porting the application design from Android to Series 40 is not that difficult as it might look at first. Series 40 phones are cost-optimized phones, yet with smartphone alike experience. The webinar addresses basic UI design aspects when porting a design from Android Jelly Bean to Series 40 full touch. (However, you should compare the UI design from Android devices with small screens (e.g. 3.2 phones) to Series 40 phones.) This is the companion wiki page.

It includes:

  • Webinar exercises (will turn into "Recommended solutions problems raised by the webinar exercises" after the second webinar session)
  • Q/A from the webinar sessions
  • Link to slide deck [will be added].
  • Link to recording [will be added]

Note.pngNote: The information is related to Android OS 4.1 "Jelly Bean and Series 40 full touch.

Webinar problems

This section contains problems raised in the webinar exercises. The recommended solutions will be added after the second session.

  1. How would you change the following structure for S40FT?
  2. How do Android Jelly Bean and Series 40 full touch differ from selecting multiple?
  3. Which device has more pixels, the Samsung Galaxy Mini S5570 or the Nokia Asha 311?
  4. Are there any limitations in using buttons in S40FT?
  5. What are the benefits of S40FT backstep paradigm?

Disclaimer

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.

425 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×