I do agree that more work needs to happen in the documentation space for Android. I don't recall the exact scenarios at this time, but I can say that a number of times I was looking to do something specific but I only found a small amount of information in the Dev Guide regarding what I was after. It was places like this mailing list, StackOverflow, and searches on Google that yielded the details and samples I was after to bring it full circle.
That said, I also created a full application that's relevant and useful to thousands of people (in a niche market even) in a very short period of time. It's not the most complicated app ever, nor is it perfect, but it's a non-trivial app with a decent following. I had an initial version of the app in the market in literally 1 week. It was not feature (vision, perhaps?) complete but it had enough to get the ball rolling and for users to see the potential. It was also not full of poor design and bugs as you might expect from such a short development cycle on a new platform. I think that speaks very well to the Android platform. As does the fact that since the initial release, I've deployed 12 updates over a span of 5 1/2 weeks. On a side note, at work I have a huge Apple fanboy who likes to compare the platforms, and I love tossing in the notion that I've deployed 13 versions of my app in such a short time frame, but I digress. :) -- Chris Stewart http://chriswstewart.com Fantasy Football<http://chriswstewart.com/android-applications/fantasy-football/>- Android app for MFL fantasy football owners On Tue, Sep 14, 2010 at 3:45 PM, TreKing <treking...@gmail.com> wrote: > On Tue, Sep 14, 2010 at 2:30 PM, DanH <danhi...@ieee.org> wrote: > >> Not really. A reference should be coherent and well-organized. >> > > What's so incoherent and disorganized about the current documentation? > Specifics might help bring more attention to the parts that need it. > > >> I've run across several diagrams of the application state flow, for >> instance, and most are clearly wrong >> > > In the official docs? Can you point them out? > > >> And descriptions (no diagrams that I've found) of the Intent resolution >> algorithm are similarly inconsistent. >> > > Can you point these out as well? > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
