Thanks for the comment, Ibendlin. I do agree, and do subscribe, to "Less is more".
As this is not an appropriate venue to discuss the development process of my app, let me just briefly outline how it went with regard to the button: 1. The elimination of "km/h" was considered and rejected as the button's function could change to adapt to the use context (e.g. "mph", "seconds", "km", etc. as I stated in the previous post) 2. Changing of button and font color according to the function, was prototyped (without "km/h") and rejected as it gets so confusing. 3. Placement of "km/h" outside of the button, right next to it, was considered and rejected for the likeliness of the button becoming too small in the available space. 4. Alternating display of "34.5" and "km/h" was considered and rejected because it forces user to wait in obtaining timing sensitive info. 5. The use of audio (to indicate the figure displayed is in "km/h") was considered, but audio is needed for another function, and the use scenario cannot eliminate the simultaneous use of the two functions. I am all ears if you could come up with a better idea, but the desire to have large "23.4" and small "km/h" did not come that lightly. Moreover, I love the challenge and the satisfaction in solving problems and limitations, which came much quicker than I anticipated in this case thanks to Mark Murphy and Zsolt Vasvari. On May 6, 8:28 pm, lbendlin <[email protected]> wrote: > Now let me throw a spanner into your work. Do some UX testing (grab a few > people that haven't seen the app before) and present them with either of > two versions, one version with the big number and small "km/h" string, and > the other version with just the number. You will find that your app doesn't > need the "km/h" string. It adds no value. Remember the principle of good > design. Less is more. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
