Yeah.  I was frustrated when I wrote that one.  I assume its a very
long shot to get into the top 50, but the first hit on the server was
like the person opened it and closed it.  Your app would have to be
horrible, or have an error, for that to be the end of the review.  You
know what I mean?

I heard back the short ones are spot checks.  So far just one actual review.

I've seen in various places that the reviews would be done by May 5.
That's like a week.  Guess this week is going to be interesting.

On Sun, Apr 27, 2008 at 11:40 AM, Incognito <[EMAIL PROTECTED]> wrote:
>
>  >"Hey
>  >man, if your app isn't getting these guys to want to use it, maybe its
>  >not good".
>
>  I'm glad you said it yourself, I was thinking the same thing but
>  didn't want to sound cynical. Crying and whining will not help your
>  case man and will only annoy everybody . There are 1700+ apps and you
>  can bet that 50 of those will be much better than the rest of the
>  other apps (including yours and mine). i.e., it will wow the judge on
>  first impression, it will not have a bug with the menu like yours, it
>  will work without a glitch, and the concept will be a good one.
>
>  Truth is, a user or judge will have made a decision about your app on
>  the first impression and if your App has a bug in the menu and or
>  simply does not seem appealing than you are screwed.
>
>
>  On Apr 26, 10:44 am, Kevin <[EMAIL PROTECTED]> wrote:
>  > I've been watching my logs, and I want to contact somebody about it.
>  > Not sure what to do.  I have a user signup process that doesn't
>  > require reading documents, but you sort of have to finish it.  I have
>  > a bug.  The user menu becomes active before the setup is done.
>  > Originally, you couldn't click around the main app until the user
>  > setup was complete.  However, I changed the app towards the end to do
>  > the menus in a common subclass, so the user setup procedure starts
>  > making the menu available earlier than it should be.
>  >
>  > So. Two judges have logged in.  The first one got about a screen into
>  > user setup, then stopped completely.  That was frustrating.  That guy
>  > just stopped.  The second one also didn't finish the setup, but then
>  > clicked around the app for a while.  At least that one got to see it.
>  > Neither did any data submission (which is what the app does), and
>  > neither logged into the exiting user I set up for the purpose of
>  > evaluation and put in the docs I sent.
>  >
>  > Most of these apps are going to be very early stage.  Its also a new
>  > type of platform for most of us (I'd bet 90%+ come from a web
>  > programming background).  What that boils down to is interface design
>  > that might not be as clear as possible.  Right?  Its easy to send a
>  > link to a buddy to take a look.  Not so easy to send an apk file and
>  > an emulator, then explain what a command line is (most of the people I
>  > have look at stuff are not computer people, which is very helpful).
>  > In my case, the screen that these guys are dropping out on has 1
>  > button, which actually says "Next".  Yet neither clicked it.  Thinking
>  > back, I should make it red or something, maybe animate it around, huge
>  > flashing arrow pointing at it.  Whatever.  But, come on.  It says
>  > "Next".  Its the only button.  Top/right of the screen.
>  >
>  > There are 1788 submissions.  I don't know how many judges there are.
>  > So that's a lot of work.  But if you figured out how much work we all
>  > put into the submissions, a total of a couple minutes is not
>  > sufficient.  At least, you know, if "Next" is confusing, have somebody
>  > send me an email.  I'll explain it.
>  >
>  > Lets imagine my app is out of the contest now, and I know from the
>  > logs that the 2 judges I got were really phoning it in (pun intended.
>  > By that I mean they're barely trying).  I'm going to have a real
>  > problem with that.  This whole 'good will' exercise would have the
>  > opposite effect.  If they gave my app a full look, and then rejected
>  > it, well hey.  Don't play if you can't handle losing.  But without
>  > really evaluating it?
>  >
>  > Anybody else have a similar situation?  The tough love answer is, "Hey
>  > man, if your app isn't getting these guys to want to use it, maybe its
>  > not good".  It isn't good.  Its alpha quality software.  Barely.
>  > Right?  Now, to be clear, I switched the app from a different one
>  > earlier.  I had a lot less time than if I'd started with this one in
>  > the beginning.  That was my decision, but still.  Its a new platform.
>  > Android is not without its own bugs.  I sort of assumed "proof of
>  > concept" was what they were looking for anyway.
>  >
>  > You know what they say about assumptions.
>  >
>  > On Apr 24, 4:27 pm, ConAim <[EMAIL PROTECTED]> wrote:
>  >
>  >
>  >
>  > > I have the same problem.
>  > > I look at the server log (which does log every activity came from the
>  > > clients). But then all I see is, the judges make the connection and
>  > > click on the Ready checkbox and then close it. When I staged clearly
>  > > on the documentation that this online poker game need at least 2
>  > > players join and ready to initiate the game. I'm not sure if the
>  > > Judges does read the documents. :(- Hide quoted text -
>  >
>  > - Show quoted text -
>  >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Challenge" 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-challenge?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to