On Sat, Jan 22, 2011 at 5:18 PM, Bob Kerns <r...@acm.org> wrote: > While I (strongly) agree with this advice -- there is a major > downside. If you copy it into your application, and the platform > changes (an update, a manufacturer customization, etc.), then your > application's look-and-feel (including terminology) will vary from the > platform standard. And, in the case up upgrades, older apps will vary > from newer ones. The result is the user experience is less cohesive.
FWIW, Google's recommendation is to aim for internal consistency first, then platform fidelity. Strings are particularly pernicious. For example, I seem to recall that the platform definition of the "yes" string is "Set", due to some screwball decision. If OEMs do that, then your app may be flat out wrong on some devices, with incorrect prompts, messages, or whatever the strings are used for. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
