canmove, Confirmed users
2,675
edits
Tantek-Mozilla-Projects: Difference between revisions
→UI Styling: comparisions
(→UI Styling: clarify ands for rich native-app UI control scenario) |
(→UI Styling: comparisions) |
||
| Line 13: | Line 13: | ||
Some data for this hypothesis: default iPhone/iPad controls are pretty enough that most developers are more than happy to use them - the default controls make their apps look beautiful, polished, without much work/tweaking (modulo layout/sizing etc.) If we can achieve that same experience with built-in controls, the theory is that most web designers will be happy to stick with built-in controls + CSS. | Some data for this hypothesis: default iPhone/iPad controls are pretty enough that most developers are more than happy to use them - the default controls make their apps look beautiful, polished, without much work/tweaking (modulo layout/sizing etc.) If we can achieve that same experience with built-in controls, the theory is that most web designers will be happy to stick with built-in controls + CSS. | ||
'''2. Rich native-app-like experiences.''' Games. Media interfaces like WinAmp. There are always going to be some user interfaces where the developer wants nearly total control of the look and feel. | '''2. Rich native-app-like experiences.''' Games. Media interfaces like WinAmp. There are always going to be some user interfaces where the developer wants nearly total control of the look and feel. Just take a look at typical Flash or Flex app UIs (note: some of those are egregiously inconsistent with the underlying OS platform just for the sake of being different - hard to avoid that but we can discourage it by making the cluster 1 solution easier and more accessible). In this case I'd like to see us figure out how to build hybrid controls that: | ||
a) Are built with the closest semantic built-in control for any particular custom control, <em>and</em> | a) Are built with the closest semantic built-in control for any particular custom control, <em>and</em> | ||