Hi *, Do you have any "official" answer regarding this fact that we had tested the ADC2 applications on 1.5 and now Android users are giving feedback based on Sdk 1.6?
Is any hope that the winners of first phase are allowed to resubmit there applications to be 1.6 ready? 10x On Oct 5, 11:23 am, Al Sutton <[email protected]> wrote: > The impression I'm getting is that there are some apps which do stick > to public APIs and still have problems. This was also the case with > the 1.1 -> 1.5 update (particularly with some layouts). > > My personal opinion is that this situation is most likely a result of > the disorganised nature of the OHA. I expect the group running ADC2 is > a different one from the one that handles distributing updates for T- > Mobile, etc., and the two just didn't talk. > > That said I don't think it's a good situation, running a competition > and stating 1.5 as the platform and then having users upgrade to a new > version of their OS is a pretty unfair. You only need to look at the > recent Mac OS X update from 10.5 to 10.6 and how it now makes the > Android SDK unbuildable on Mac OS X to see what *can* happen with a > "minor" version upgrade. > > Truth of the matter is though; It's happened, and all the ranting and > raving in the world isn't going to get T-Mobile and the rest to push > 1.5 back out to downgrade users just so ADC2 can carry on, so I think > the point has been made and we all need to move on. > > Al. > > -- > > * Looking for Android Apps? - Tryhttp://andappstore.com/* > > ====== > Funky Android Limited is registered in England & Wales with the > company number 6741909. The registered head office is Kemp House, > 152-160 City Road, London, EC1V 2NX, UK. > > The views expressed in this email are those of the author and not > necessarily those of Funky Android Limited, it's associates, or it's > subsidiaries. > > On 5 Oct 2009, at 08:56, Spencer Riddering wrote: > > > > > First of all, this isn't true and second its beside the point. > > > How many ADC2 applications need to be affected before its considered a > > real issue? My application no longer works correctly under 1.6 and I > > only used public APIs. Is that enough? (Yes, the bug was submitted > > and the problem acknowledged) > > > What do you think should happen to a developer's app if they > > accidentally used a non-public API? > > > Again, my point is that the preferred judging platform version is 1.5 > > and encouraging it's use whenever safe is the right thing to do. > > > Do you disagree? > > > Spencer Riddering > > > On Oct 5, 12:17 pm, Raphael <[email protected]> wrote: > >> Out of curiosity: how many developers of adc2 apps tested their apps > >> under the 1.6 emulator and actually found any issue? > > >> If the app is using public APIs and/or the 1.5 NDK, it should work > >> fine under 1.6. If not, make sure to file bugs athttp://b.android.com > >> so that issues can be addressed. > > >> R/ > > >> On Fri, Oct 2, 2009 at 7:20 PM, Spencer Riddering > >> <[email protected]> wrote: > > >>> My point wasn't to sound an alarm. It was intended to be thought > >>> provoking. > > >>> I want to remind Google that IMHO the preferred judging platform is > >>> 1.5 so anything they can do to tip the scales towards using 1.5 is > >>> the > >>> right choice. For example, will the industry professional judges in > >>> round 2 be asked to use devices running 1.5 if possible? > > >>> My point was also a bit reflective. How did we get here? How can > >>> this > >>> situation be avoided in the future? > > >>> On Oct 3, 12:05 am, Spencer Riddering <[email protected]> wrote: > >>>> It's only a week into the ADC2 judging and already phones are being > >>>> updated to Android 1.6 Cupcake. With at least one more week to go > >>>> in > >>>> the first round and (I'm guessing) two more weeks of judging in the > >>>> second round this means that around 75% of the ADC2 judging will > >>>> occur > >>>> on Android 1.6. The 1.6 SDK was not made available to developers > >>>> until > >>>> after the ADC2 deadline so (except for a few exceptions) all of the > >>>> ADC2 applications were not tested on this judging platform. > > >>>> Already an undocumented change in 1.6, which can break applications > >>>> that worked on 1.5, has been discovered > >>>> herehttp://groups.google.com/group/android-developers/browse_thread/threa > >>>> ... > >>>> and Google has acknowledged the problem > >>>> herehttp://groups.google.com/group/android-developers/browse_thread/threa > >>>> ... > > >>>> Why is Google allowing an estimated 75% of the ADC2 to be judged > >>>> on a > >>>> platform version that almost no one has had a chance to test on? > > >>>> Spencer Riddering --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
