Establishing the feature phone guidelines

Since we’re developing a smart phone capability enabled feature phone with physical keys from the ground up, it is vitally important to produce a set of thoroughly detailed and efficient guidelines to use as the backbone for all future iterations.

These guidelines describe in detail of the overall physical key behavior, common UI component purposes, general patterns (such as navigation through items, selecting items, processing etc.) and audio channel competing rules that are applied in H5OS for the smart feature phone.

Many problem solving revolved around balancing the visual design and usability. Due to the nature of the device input, navigation visual cues has to be explicitly clear, as almost every key press will result in changes of focus or screen status. For instance when there's a disabled function in the list item format, the focus visual indicator has to be able to allow the user to see the state at a glance. We also made many attempts to strike a balance between creating a spacial look & feel and utilizing the limited screen space. The dimensions of each UI elements were carefully designed through multiple iterations.

Main contribution

• Set up guideline for overall common component, system responsiveness evaluation standard and audio channel competing rules.
• Designed and created guideline documents for the above items.
• Worked closely with visual designers to create the best UI with both aesthetics and usability .
• Worked closely with developers to discuss the feasibilities of features and potential solutions.
• Worked closely with QA members to assure the quality of H5OS smart feature phone.