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. Say what you will about Apple but having a super tight target platform makes everyones life so much easier. Heck, just look at the dominance of consoles.
roll on SenseUI build MotoBlur build Vanilla build On Oct 26, 11:54 pm, JP <[email protected]> wrote: > Thinking about this more I suppose I'll issue Verizon-only releases, > and solicit the input from users to find out if and how 2.0 on Moto > breaks the apps. > Geez we're getting pushed into pretty shitty practices here, or > perhaps that's the acceptable standard now. > > On Oct 26, 4:38 pm, momo <[email protected]> wrote: > > > > > I can't agree more. Release beta SDKs for each of your releases for > > developers or any developers who already has an application in the > > Market. As changes are being implemented, update the beta SDKs to new > > versions. This way developers are GIVEN MORE TIME to verify that > > their apps work. > > > Sigh sometimes I feel the Android team is run very poorly. > > > On Oct 26, 4:22 pm, JP <[email protected]> wrote: > > > > If this is true... insulting to those that conduct open source > > > development truly open source. > > > > Makes me consider to change the licensing of the stuffs I've released > > > on Apache 2.0 back to GPL. > > > > On Oct 26, 2:30 pm, wimbet <[email protected]> wrote: > > > > > If Google likes your app, you can get early access to the Android 2.0 > > > > code. > > > > >http://androidandme.com/2009/10/news/google-hand-picks-developers-for... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
