..but they may need a specific build for 2.0. Certainly all the past updates have impacted app developers in both intentional and unintentional ways. "Block out vendors and carriers that may be broken" is a good answer from both the "pay for stupidity" perspective as well as "don't get a ton of bad ratings because your app broke on 2.0" (And by 'pay for stupidity' I mean that 2.0 is secret and hidden because they insisted on such. Really funny that they probably paid extra for the abuse they're about to receive from users and app developers, not to mention those of us trying to work with android open source.)
On Tue, Oct 27, 2009 at 10:12 AM, Mark Murphy <[email protected]> wrote: > >> That's a slippy slope to start on JP, not long until we're building >> for vendor specific custom OS's and then versions of those OS's. > > You don't need to do that. > >> roll on > > It is unclear what deodorant delivery mechanisms have to do with Android. > >> SenseUI build > > Apps do not need a dedicated build for HTC Sense. > >> MotoBlur build > > Apps do not need a dedicated build for MOTOBLUR. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > Android App Developer Books: http://commonsware.com/books.html > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
