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 held in October 2012. It covers both sessions (4 October 2012 and 10 October 2012).
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.
- 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]
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?
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.