The documentation is intended to be a place where you can put information that judges will need to see to accurately judge your application. It does not need to contain any technical information, like architecture or design.
You should include a brief description of what your application is and does, but other than that whatever it contains is up to you. If you had to work around any problems with the SDK (such as with the Media Player, which unfortunately has a few known issues, or with GPS) you should mention them in your documentation file. - Dan On Fri, Mar 28, 2008 at 11:56 AM, everfriend <[EMAIL PROTECTED]> wrote: > > (I know the answer is always: depends.) > > Is there a general guideline/advices? > > Specially, do we need explain our application architecture, code > structure, etc? > > This question is kinds of relating to how an application will be > evaluated? Will the code and application design/structure be evaluated > also? If so, we need put more info about the application architecture/ > design in the attached document, and/or more comments in source code > (assuming the .apk file can be reverse-engineered, not sure about it > though). > > Hope to hear some advices/comments. > > Thank you, > > Ever. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
