download

275 views
230 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
275
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

download

  1. 1. S^4 User Interface Concept Proposal Contents Document Information.............................................................................................................2 User Interface Concept Proposal............................................................................................2 Description...........................................................................................................................2 Benefits...............................................................................................................................3 Benchmark..........................................................................................................................4 Visualize..............................................................................................................................5 Localization..........................................................................................................................5 Languages.......................................................................................................................5 User feedback elements..................................................................................................5 Hardware/key mapping....................................................................................................5 Dependencies......................................................................................................................6 Exclusions...........................................................................................................................6 Revision History......................................................................................................................6 Appendix.................................................................................................................................7 Criteria for the User Interface Concept Proposal review process.........................................7 Criteria for rejection..........................................................................................................7 Criteria for approval..........................................................................................................7 1
  2. 2. Document Information S^4 User Interface Proposal Development Proposal ID <Insert ID> Status Proposed User Interface Concept Proposal Description The S^4 user interface primary objective is to simplify the S60 user experience by: - renewed layouts (see Butterfly Diagram below) - context menu support for list items - flattened command distribution with elimination of ‘tunneling’ Options commands - Applications Library replaces Main Menu - four user-facing libraries: Contacts, Music, Photos, Applications - Homescreen supports irregularly shaped Homescreen widgets, free placement of Homescreen widgets, and improved move and delete functions for Homescreen widgets - guidelines for autosaving content reduce Save commands - improved task switcher minimizes Exit commands and provides improved visual access to backgrounded ‘continuous experience’ applications (e.g., music playback, active call, etc.) - prompts to users minimized - redesigned Control Panel and settings/personalization information architecture - refocused Power menu includes master volume and vibra on/off controls - interaction and layout patterns applied to all applications Titlebar Region Content Region Controlled by the System. Contains Controlled by the Application. three interactive elements: Contains arbitrary contents: 1) Universal Indicators button 1) Can be populated with one or more shows network signal strength & content items. When the content battery strength, touch to invoke displayed is within a hierarchy, the notification panel optional Label Field placed below the Titlebar notes the user’ s location. 2) Title/Menu shows application title, touch invokes dropdown 2) Content panel has a configurable Options menu scrollbar 3) Back button, touch to back 3) Toolbar is optional, max 4 buttons, navigate through the application’ s can have extensions back stack then Home or Task Fig. 1 Symbian Devices Butterfly Diagram
  3. 3. Titlebar may autodismiss with application toolbar. Default animation is up and off screen. Application toolbar may autodismiss with titlebar. Default animation is down and off screen. Fig. 2 Symbian Devices Chrome Dismissal Behavior Dialogs Dialogs are Z-ordered above the Content Region using one of three template sizes and may be full-screen. Dialogs animate in and out according to the transitions specified in the transition and effects language. Fig. 3 Dialog ordering Benefits This proposal improves the competitiveness of the Foundation Platform by reorganizing and clarifying the feature richness of the software to improve access to and use of richly interconnected applications. Note that this UI Concept proposal institutes new design guidelines for S^4. Layout simplification places first order commands (used most frequently by users) in the primary application view, second order commands under the Options menu or in Settings. End users can see the main commands of each application as soon as it is launched.
  4. 4. The titlebar is provided by the system and is the access to the Options menu. The number of commands in the Options menu is typically limited to 6 to prevent scrolling of the menu in landscape orientation. Cascading menus are permitted and there is no guideline limitation on extending the Options menu to a number of menus. However, the titlebar is supplied by the system and its real estate is not available to the application. The titlebar reflects the application title. A label field placed immediately below the titlebar can indicate the user’s location in a hierarchy, and is typically used whenever the user enters a collection. The number of layout files per application has been reduced: an application typically has 3-5 layouts including a list view, item view, and edit view. End users can easily recognize features and find them onscreen in a predictable location. The combination of these two factors streamlines the number of clicks to complete tasks. A Context menu invoked by a long press to a list item provides an accelerator to commands located in the item’s full screen view. End users can access commands such as Delete Item without navigating to the item. Screen real estate management is simplified by initially exposing application ‘chrome’ (titlebar area and optional toolbar) and autodismissing for media applications (chrome is reinvoked with a touch to the screen). Applications requiring fullscreen viewing can take advantage of autodismissing chrome. End users see the availability of controls and can easily invoke them; toolbars do not need to reserve persistent screen real estate. The Library Pattern recommends a flat, ordered list of content plus the ability to create dynamic or static collections within each library. The four end-user facing libraries on device employ the Library Pattern and Index scrolling to quickly reach a target location in an ordered list: a letter of the alphabet for alpha-ordered lists, or a date for time-ordered lists. Flattened hierarchies make it easier for end users to find and manage their content – applications, contacts, photos, music – without nested folders. (Note that the TreeView widget supports nested views where required). Filtered views are presented as static collections (photo albums, music playlists, contact groups, application collections) or dynamic collections (e.g. recently added, downloaded, purchased). Multiple filtered views can be created by users or provided by default. Shortcuts can be placed on the Homescreen providing easy access to specific content items or collections. The proposal references a pattern library that replaces the existing S^3 style guide. Current design guidelines are provided in the Symbian Devices Pattern Library (under development) and include interaction patterns and descriptions of available Orbit widgets. Previous User Interface Style Guides are deprecated. Benchmark User interface design solutions that exist for other operating systems are similar in the following respects: - HTC Hero and Motorola Droid, both on Android, have a Homescreen with movable Homescreen widgets; however, each has one multi-panel homesceen page, whereas Symbian Foundation has independent unique pages - Palm Pre’s WebOS eliminates Exit commands, but instead of saving state and releasing memory it keeps applications running - iPhone has a flattened application library; however, it is displayed to the user exclusively as a manually organized grid, whereas the Symbian Foundation application library is an alpha- ordered list with multiple filtered views.
  5. 5. Visualize Fig. 4 Homescreen Fig. 5 Photos Fig. 6 Video playback Note: Application ‘chrome’ supports transparency. Localization Languages This proposal refers to standard layouts and interaction principles and does not cover localization. User feedback elements This proposal includes reference graphics for theming and the standard contributed set of icons. All images may be replaced. Hardware/key mapping The solution requires a mechanical Home key, Send/End keys, and volume Up/Down keys. The Camera application requires a mechanical capture key. Additional keys recommended but not required include Back, Options, Power, and a lock mechanism (button or slidelock). Power may be mapped to the End key but certain conditions apply. A mechanical navigation element for moving focus within a text edit field is highly recommended (e.g. a 5-way navigation cluster, roller/select component, or arrow keys).
  6. 6. Dependencies There are no dependencies to other User Interface Concept Proposals. S^4 layouts are prepared in 9:16 aspect ratio (portrait dominant), 3.2” display dimensions. Deploying current assets to alternate aspect ratios or screen dimensions may require alterations to application layout files. Default images and theme elements provided with the interface proposal are rendered in a reference theme. The reference theme primary color is black and is for illustrative purposes only. The theme should be replaced for production to devices. Exclusions There are no known exclusions. Revision History
  7. 7. Appendix Criteria for the User Interface Concept Proposal review process This section provides useful information on how to prepare a User Interface Concept Proposal and what to consider in order to making it more successful in the acceptance process. Added are both acceptance and rejection criteria’s. Criteria for rejection A User Interface Concept Proposal is likely to be rejected if: • The User Interface Concept Proposal potentially infringes legal copyright and patents owned by a company not a member of the Symbian Foundation (e.g. unacceptable / unnecessary imitation of other products, limitation of trademark or logos of other companies iconography or graphics) • The User Interface Concept Proposal makes use of User's personal data and does not demonstrate what methods will be employed to ensure it is protected • The User Interface Concept Proposal differs in scope of the corresponding, approved development proposal – The UI Council may conditionally approve a User Interface Concept Proposal that differs in agreed scope given the condition that the FRC agrees to the new scope. The FRC shall in these cases be notified in order for the adequate proposal content to be discussed and approved. • The User Interface Concept Proposal interaction paradigm is significantly different and threatens consistency of the Symbian Foundation user interface (e.g. violates more than one aspect of the guidelines to the point that it is basically unusable, fundamentally not authored for a mobile environment or the Symbian Founcation Platform, etc). – This criteria is to prevent external inconsistency developing within the Symbian Foundation Platform user interface between different applications. It is important that this criteria is not confused with a limitation in acceptance of contributions of new interactions styles and paradigms that will drive innovation into the foundations user experience. • The User Interface Concept Proposal is not interoperable to the degree that it interferes with or disables any other functionality on the phone. Criteria for approval A User Interface Concept Proposal is likely to be approved if it is: • Easy to understand according to the norm and standards of the target user population • Easy to use • Efficient to use • Follows the Symbian Foundation User Interface Style Guides where appropriate. (e.g. does not contain inadequate or inconsistent use of components) • The Symbian Foundation design philosophy is met • The User Interface Concept Proposal is supported with research into user wants and needs
  8. 8. • The User Interface Concept Proposal follow industrial usability standards (e.g. ISO9241 etc. Ref: http://www.usabilitypartners.se/usability/standards.shtml) Additional criteria for new controls or interaction styles • the User Interface Concept Proposal demonstrate sustainability • the User Interface Concept Proposal demonstrate extensibility of future scope through road mapping or trend forecasting • the User Interface Concept Proposal is an enabler that lays down a foundation for future innovation

×