To me, the right thing to do would be to stop the first phase of this contest now, select the to 200 apps, figure out which ones bomb from 1.6 and give the developer a change to only change the bits that are causing the problems. There would have to be some controls to prevent upgrades and assurances to the rest of the developers that nothing else was changed to improve their apps or allow everyone to update, which would probably really annoy the heck out of anyone who figured out they had a problem on September 2nd and didn't make it to the finals.
On the other hand, if your apps are failing because you used undocumented options in the SDK, then you only have yourself to blame... -John Coryat "Radar Now!" "What Zip Code?" On Oct 5, 2:18 pm, bellapariah <bellapar...@gmail.com> wrote: > Someone from Google please comment or at least give contact info! My > issue has to do with one of Google's API changes for 1.6 so it isn't > even a programming error on my part. I'm sure my ADC2 entry will get > low scores from everyone that upgrades to 1.6 since they can no longer > join rooms (calling issue with 1.6), and therefore cannot test the > app. Google should at least issue a statement letting testers know > that upgrading to 1.6 may cause some apps to stop working and to > please skip these so that 1.5 testers can give them an accurate > review. > > Has Google completely abandoned this contest? Why have they not been > actively participating, answering developer questions, and building > buzz and excitement around the contest? This contest is supposed to > persuade programmers to develop for Android, not screw them over after > months of hard work then ignore them when their is a problem. Maybe if > their are enough developers affected we can get the attention of tech > sites and get some publicity for the issue. > > Shelby > > On Oct 4, 11:31 pm, bellapariah <bellapar...@gmail.com> wrote: > > > I just got the 1.6 download and found out myADC2app is not working > > anymore. Works fine on 1.5 but people with 1.6 can't log in. Guess > > that explains the sudden drop in new accounts being created (We got > > around 70 testers before numbers plummeted to 5 to 6 over the > > weekend). :( If Google planned to release 1.6 in the middle of a > > contest, they should have informed developers and given them the tools > > to test their app on this platform. We spent months on creating a high > > quality app for this contest and now people can't even judge it! There > > are probably hundreds of other developers that spent sleepless nights > > working their butt off to finish before the deadline just to have > > their chances decimated by google. All I can say is that I'm extremely > > disappointed in the way Google has handled this entire contest and I > > think it is extremely unfair and inconsiderate the way they are > > treating developers that they are supposed to be attracting to the > > Android platform. > > > Shelby > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
