the more voters, the
better for the contest.
I don't believe so. A smaller number of qualified testers would yield
a more reliable result than a huge number of people who do not know
how to develop software. No one will concede to the developer that the
app crashes because of Donut - in fact,
I don't believe so. A smaller number of qualified testers would yield
a more reliable result than a huge number of people who do not know
how to develop software. No one will concede to the developer that the
app crashes because of Donut - in fact, he can't tell whether it's the
app or the
Right, I think he's suggesting however, that the issue is with 1.6.
A random user who gets the app and has it crash immediately won't think Oh,
this likely has something to do with the recent update to my phone, I'll
skip judging. They're more likely to think Crashed, sucks, 1star. Which
leads
expert judging is a good idea when the judging can be detailed and
specific. When judging is limited to 1-4 stars over 4 vague
categories, large numbers are best.
On Oct 6, 2:37 am, walthes andreas.walt...@googlemail.com wrote:
the more voters, the
better for the contest.
I don't believe
On Fri, Oct 2, 2009 at 19:15, Georgios Galyfos yorg...@gmail.com wrote:
I am sorry for asking this. I assume the developers taking part in the
challenge are allowed to judge in the contest, but this way they would be
allowed to judge even their own app, right? I havent used the judging app
Compatibility with 1.6 could be a real problem for ADC2.
Yesterday I got the update to Donut on my G1. I had installed the ADC2
judging app a couple of days before. The judging app still works fine.
Last night I downloaded an entry called OpenGesture. It force crashed
over and over. I'm unable
On the other hand...
For those that had a submission with a terminal error, it will put
doubt into the minds of the judges as to the cause of the error: poor
programming or 1.6.
-John Coryat
What Zip Code
Radar Now!
--~--~-~--~~~---~--~~
You received this
On Fri, Oct 2, 2009 at 16:18, polyclefsoftware dja...@gmail.com wrote:
it is poorly designed, or because of compatibility issues with 1.6. I
gave the developers the benefit of the doubt and gave the app an
overall 3 star rating.
Best (fairest) thing to do when you suspect behavior may have
That makes sense. I knew we could skip installation of apps, but
didn't know I could skip voting as well.
I'll do that from now on.
I haven't tested my entry under 1.6, so I don't know if there are
issues. Your average user probably won't care if it doesn't work
because of the OS version,
But you would hope the number of developers voting would be significantly
less than number of random users. And unfortunately, they very well might
not think Oh, this could have something to do with the recent update and
skip. They'll just give a 1 star.
- Dan
On Fri, Oct 2, 2009 at 12:05 PM,
I am sorry for asking this. I assume the developers taking part in the
challenge are allowed to judge in the contest, but this way they would be
allowed to judge even their own app, right? I havent used the judging app
yet, being afraid to risk disqualification of my entry. The terms dont state
Which it does.
On Sep 30, 6:44 pm, Maps.Huge.Info (Maps API Guru)
cor...@gmail.com wrote:
The only fair solution would be to make sure the judging app doesn't
function on 1.6
-John Coryat
What Zip Code?
Radar Now!
--~--~-~--~~~---~--~~
You received this
On Sep 30, 11:00 am, ander...@phdgaming.com ander...@phdgaming.com
wrote:
The second round of judging also includes user judging - 40% of the
outcome if I remember correctly.
I believe you are incorrect on this. This first round of judging is
user judging, and makes up 40% of an apps
From http://code.google.com/android/adc/adc2_terms.html
Ooops, looks like I had it wrong. Thanks for the correction - had
missed that previously. :)
This does present a bit of an interesting situation. The HTC Tatoo
coming out in October has a 240X320 screen the smallest of any
mainstream
It would appear 1.6 is now being rolled out to all T-mobile users
(
http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidGeneralthread.id=6733
and most android news sites). Ouch for those who happen to have
application problems under the new release.
Crashing on unofficial builds is worse than crashing at startup on official
builds? =P
- Dan
On Wed, Sep 30, 2009 at 1:49 AM, Pieter pie...@gamesquare.nl wrote:
The problem is a little worse for us. Our app does runs fine on 1.6 in
the simulator, but we got complaints about crashes from
On Wed, Sep 30, 2009 at 01:58, b2amedina b2amed...@gmail.com wrote:
If the rumors are true and Donut does become available next week won't
that make judging unfair since some judges may be using 1.6
The 1.6 SDK was made available on Sept 15 and the ADC2 submissions
closed Aug 30th.
Donut
The second round of judging also includes user judging - 40% of the
outcome if I remember correctly. So the likelihood that a significant
number of judges will be running 1.6 before all judging ends is quite
high in my opinion.
Warren
On Sep 30, 6:54 am, Cédric Berger cedric.berge...@gmail.com
The only fair solution would be to make sure the judging app doesn't
function on 1.6
-John Coryat
What Zip Code?
Radar Now!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this
The second round of judging also includes user judging - 40% of the
outcome if I remember correctly.
I believe you are incorrect on this. This first round of judging is
user judging, and makes up 40% of an apps final rating. The second
round is all expert judging by Google that counts for the
+1 judging app shouldn't function on 1.6
ADC2-Round1 should end before 1.6 official upgrade.
Existing judging app should not be used for ADC2-Round2 (create a new
version) and...
neither should the new judging app (round2) function on 1.6
On Sep 30, 8:44 pm, Maps.Huge.Info (Maps API Guru)
The problem is a little worse for us. Our app does runs fine on 1.6 in
the simulator, but we got complaints about crashes from people running
unofficial builds:
java.lang.ClassCastException: android.graphics.drawable.BitmapDrawable
at
22 matches
Mail list logo
