That's my understanding too. Every software has bugs, including those Google software.
On Fri, Apr 25, 2008 at 4:40 AM, David Moffett <[EMAIL PROTECTED]> wrote: > > My app probably had some bugs and omissions, that is the nature of the > game. I am guessing even Android might have a bug to two? :-) > > Really the bottom line is, imo, will your app show off Android and > help sell phones? Pure speculation on my part but if an app showed > huge potential and would help Android be successful then you have a > winner. > > David > > On Apr 24, 2008, at 1:53 PM, Cow Bay wrote: > > > > > your message raises a question of mine about round 2 of Challenge I: > > > > "how complete must the app be in order to win $270k or $100k?" > > > > it is especially critical to those client/server apps that currently > > "fake" > > server code/data in the apps. > > > > it will be great if anyone of google could answer it. > > > > ----- Original Message ----- > > From: <[EMAIL PROTECTED]> > > To: "Android Challenge" <[email protected]> > > Sent: Thursday, April 24, 2008 10:23 AM > > Subject: [android-challenge] Re: How many people submitted with > > known bugs? > > > > > > > > Ours showed a concept, a user interface and a roadmap. We presented > > the problem as worth addressing and well posed with Android. Our > > server side is to act like another android phone using the GTalk > > interface to communicate with the handset. This keeps important > > background processes on the mobile phone light enough to hold priority > > and not get frozen and keeps valuable information about when and where > > you travel secure on the server Android. Testing would require > > multiple emulator instances which we thought was beyond the scope of > > the testing for phase 1. So we have left the judges with a question: > > Is it worth while to progresively engage commuters in community in a > > step by step way? > > > > We did not provide a complete solution, just user interface and proof > > of principle. A time and space travel demo would have been more > > persuasive, but we showed that with a video. So I would not say bugs, > > it is a proof of concept protoype consistent with resources we had at > > that time. > > > > Ed > > > > > > > > On Apr 24, 12:34 pm, "Steven A." <[EMAIL PROTECTED]> wrote: > >> Depends - do missing features count as bugs if the application > >> functions without them? If so, stuff like music, score upload, pause > >> functionality, etc are all bugs in my submission. I only started / > >> learned the contest existed in mid-March, so I got hit by a lack of > >> time to fully debug things that didn't work right away and hence were > >> dropped for the submission. Stuff like the lack of MIDI support (the > >> same code now works when I switched the music to mp3s..... I'm still > >> quite upset at myself for not thinking about trying this earlier). > >> > >> Like Kornelius, a week later my app is many times better than what > >> was > >> submitted and I'm wishing I had submitted that instead. ^^ I update > >> it > >> every couple of days at:http://www.phdgaming.com/c/EDUBlaster.apk > >> (http://www.phdgaming.com/Games/EDUBlaster.cfmfor the main > >> application page). Even though I'd feel much better if the new > >> current > >> prototype version had been submitted..... I also realize I can't > >> change the past, and can only hope I make the top 50 cut with what > >> was > >> submitted. :) > >> > >> On Apr 24, 1:15 pm, Kornelius Tuggerson <[EMAIL PROTECTED]> > >> wrote: > >> > >> > >> > >>> A whole bunch of small stuff slipped by me during the presubmit > >>> crunch. I used the weekend after the challenge to address them and > >>> my > >>> app became a 100 times slicker and more usable. > >> > >>> I am kicking myself now because I didn't allow myself enough time to > >>> polish the ui up before april 14th. Why didn't I follow the agile > >>> approach? Why didn't I deliver a working product more often? Why > >>> did I > >>> let my model and my view code get all tangled up together? Because > >>> made the mistake of thinking that developing code on my own time is > >>> somehow gonna be easier or more pleasant then developing code at > >>> work. > >>> Boy was I wrong. > >> > >>> Anyway to the 15 people who downloaded the ADC version of my app - > >>> try > >>> the new one, its faster and less buggy, and works an all emulator > >>> screen sizes!http://code.google.com/p/android-geocast/ > >> > >>> On Apr 24, 12:47 pm, Chris <[EMAIL PROTECTED]> wrote: > >> > >>>> I see a lot of posts from people worried about a bug or two that > >>>> slipped through. My gut tells me almost all of us have bugs that > >>>> made > >>>> it in with our submissions and that they are expected. If you > >>>> submitted your app with bugs in it make a post in this thread. > >> > >>>> I'll start: > >> > >>>> +5 or 6 issues we didn't have time to fix- Hide quoted text - > >> > >>> - Show quoted text -- Hide quoted text - > >> > >> - Show quoted text - > > > > > > > > > > > > > > -- take care, Muthu Ramadoss. http://mobeegal.in find stuff closer. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
