Don't let your schedule get in the way and just give it a try -- you don't have anything to loose! Just prioritize your feature set from an end user perspective.
You have till the 31st to submit.
R/ (sent from my magic phone)
On 2009 8 25 12:11, "Steeler" <cowbo...@yahoo.com> wrote:
NOOOOO!!
Oh well. I was hoping it would be postponed, because I didn't even
hear of it (nor did I even hear of Android itself) until about the
beginning of August. I crammed to learn the basics of Android
development, and it seemed that everything worked out just enough...
earlier this Summer I had learned some Java and game programming
basics, and I taught myself more as I went... but my project is only
2/3 done. I can probably still enter it, but a postponement would have
been really nice, and seems merited anyway if they put off posting the
entry page by almost a month.
On Aug 24, 10:10 pm, Muthu Ramadoss <muthu.ramad...@gmail.com> wrote: > Great news, Thanks! > > tak...
> http://linkedin.com/in/tellibitzhttp://androidrocks.googlecode.com- Android Consulting.
> > Sent from Tamil Nadu, India
> Charles de Gaulle<http://www.brainyquote.com/quotes/authors/c/charles_de_gaulle.html>
> - "The better I get to know men, the more I find myself loving dogs." > > >
> On Mon, Aug 24, 2009 at 11:47 PM, Ralf <ralfo...@gmail.com> wrote: > > > Just in: >
> >http://android-developers.blogspot.com/2009/08/android-developer-chal...
>
> > HTH
> > R/- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are sub...
Depends on what your feature set is. The point of the challenge, if I
read the blog post correctly, is to have applications that are judged
as good by the end-users. Say you envisioned your app to do X, Y and
Z, which _you_ deem as the bare minimum, but would a user find the app
useful if it were to do on X? Most of the time, yes. It's probably
better to have a solid feature X than half-baked features X, Y and Z.
It's actually good, it leaves room for the app to evolve, users like
that too.
When I develop my hobby apps, I plan my iterations on advance -- I
generally start with a broad list of features, start with the bare
minimum and then iterate. Otherwise I'd never ever get my apps
finished nor published -- heck I never created an app and though it
was "finished".
R/
What I meant was that my app has 2/3 of the coding needed to call it publishable. It's a game... right now I really just have the engine (controls, physics, placeholder graphic squares, collision detection*) built. I need to work with animations, make some levels (not as scary as it sounds, the way my game works), and add polishing things like a menu and a scoreboard. Then I've also got to learn to sign apps, make a 3D icon that follows their rules, etc.
If I counted all the little features I wanted to add (and may well add to the full market version later), I wouldn't even say 2/3. --- On Tue, 8/25/09, Ralf <ralf...@gmail.com> wrote: |