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.

(Difference between revisions)

Mobile Design Pattern: Scalability

From Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata etc)
hamishwillee (Talk | contribs)
m (Text replace - "Category:Mobile Design" to "")
Line 21: Line 21:
|author= [[User:Rahulsingh1m]]
|author= [[User:Rahulsingh1m]]
[[Category:Usability]][[Category:Mobile Design]][[Category:Mobile Design Patterns]]
[[Category:Usability]][[Category:Mobile Design Patterns]]

Latest revision as of 03:26, 9 May 2012

Article Metadata
Created: User:Rahulsingh1m (30 Jun 2009)
Last edited: hamishwillee (09 May 2012)


[edit] Description

Scalability refers to the ability of the application to adapt to different screen sizes and orientations.

Messaging application example with scalablility
Messaging portrait.jpg

Messaging landscape.jpg

[edit] Use when

  • When effective usage of screen space is required.
  • To provide rich experience to the user.

[edit] Benefits

  • Different variants of application not required for different screens.
  • Some applications like browser can be used much better in landscape mode.
  • Less effort required to support the application on a new device.

[edit] Design Tips

  • Built in system components already supports scalability.
  • Custom components should be designed and tested properly for scalability.
  • Orientation change can be initiated through a hardware event and also through the application.
  • On change of orientation, the application should continue normally.
  • In case a particular screen is not supported, proper error dialog should be displayed to the user.
  • Application data like text, images should be rendered properly for different screens and should be easily readable by the user.

[edit] Related Links

This page was last modified on 9 May 2012, at 03:26.
30 page views in the last 30 days.