Dan, Please note that this reply is NOT meant to be inflammatory, so please don't take it as such.
Perhaps you guys (Google, OHA) didn't completely think this one through. You wanted developers to create applications for the Android platform that would differentiate it from the other mobile platforms. However, did you ever consider that such differentiation could come about via the development of software designed to support a mobile Android device that doesn't actually run on that device? What if part of the differentiation, and the draw for an application, comes from its ease of installation versus existing mechanisms for doing the same thing on other platforms? I know that this sounds kind of vague but it's a very important point. For a concrete example of what I'm talking about please check out my submission (it will be under Adam Spencer). There is a flash video at my site (referred to via the documentation for my submission) that demonstrates my point much more clearly. The reason I'm not giving the site out here (in a public forum) is because it's only meant for ADC judges at the moment. The reason why I want you to check it out is because I believe that a huge part of the "public appeal" of my app is the simplicity for the end (non-technical) user in regard to using it - which includes installation. However, this is something that can only really be appreciated by a judge actually walking through the install process. You wanted us to think out of the box for this contest, I did ... and now I kind of feel like before the judging even really gets started I've been punished for it. Was it documented somewhere that judges would not be a part of the install process for the apps? If it was then I missed it. If not, then you just eliminated some segment of your submitted applications based on criteria that weren't previously disseminated. Sure, maybe that segment is small but those could be some of the best apps! regards, Adam On Apr 8, 11:08 am, "Dan Morrill" <[EMAIL PROTECTED]> wrote: > Hi, Mark! > Each application will be tested separately in a clean installation of the > emulator (i.e. using the -wipe-data option.) Judges will not be able to > install pre-requisite or dependency .apk files. > > You should definitely package your application (including all platform > components) into a single .apk file, one for each submission. > > - Dan > > On Tue, Apr 8, 2008 at 7:26 AM, whitemice <[EMAIL PROTECTED]> wrote: > > > >>...we will test all of the submissions to make sure that they actually > > run on the version of the emulator specified in the submission > > application...<< > > [The Android Developer Challenge Judging Process] > > > I have made an "application platform" and will be submitting a number > > of separate entry's that require this to be previously installed on > > the emulator in order to run. I.e. install executable (a) then > > install executable (b). > > > If you try and first install executable (b) it will show a "helpful" > > error message saying you need to first download executable (a) from a > > website. I will include this file as part of the documentation ZIP, > > as well as document the installation process the readme file. > > > Is it likely that some of my non-standalone applications be rejected > > out of hand (i.e. by the poor guy who has to test each of the > > thousands of buggy submissions)? > > > Regards > > Mark --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
