Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Kshitij Sinha
3,186 PointsHow much documentation of Android classes do you recommend one reads?
I was wondering about the documentation, there are so many classes and hence even more methods one can use. So how much does one read? Anything mandatory?
6 Answers
Ben Jakuben
Treehouse TeacherGood answers here! I like to read some of the overview documentation and then use the docs as reference material when I'm trying something new. For Android specifically, I'd recommend reading the first section of the Design Guidelines and some or all of the Introduction and App Components section of the API Guides. Then you can start to pick and choose topics as you need them or want to learn more about them, like Content Providers, for example.
Jeremy Martin
Courses Plus Student 2,521 PointsI recently did some research, similarly, to locate a list of Java classes and methods so here is my take on the matter from what I was able to find(and not find). Because there are thousands of Android-specific classes in addition to even more Java classes and methods which can be used in Android applications, exploring the options provided by the auto-complete feature in your IDE or Android Developer Tool (ADT) would be your best bet.
This feature provides a list of classes as well as method variations (methods with different combinations of constraint) with a description based on the text you type in the ADT.
For example, type 'get' in the ADT and then press Ctrl + Space, then Tab to explore the proposal table with the arrow keys.
Also try typing 'on'. It even works using just one letter as well for a more extensive list.
This certainly helps cut down on the number of keystrokes during development as well. :)
Check out http://developer.android.com/reference/classes.html
Hope this helps!
rll
4,166 PointsMaybe Ben or ? could chime in on this because this is a great question. I personally think research skills trump all when it comes to this. One can't possibly memorize all of the methods, classes, etc. to the point of not needing to refer to the documentation. This leads me to believe that it really isn't about the individual parts that make up an app. It's about knowing in general terms how the sum of the parts go together. That is just IMHO..
Kshitij Sinha
3,186 PointsJeremy Martin I am sure that helps but what exactly should one "HAS to know" under all circumstances. Roland L. Leljedal, I hope Ben could shed some light on this. Ben Jakuben what do you think? How much documentation is like "mandatory to know". How did you go by it?
Jeremy Martin
Courses Plus Student 2,521 PointsI would agree with Roland. Having any certain number of methods and class memorized would be secondary to understanding the more general parts that make up an app and how to make them work together. Some of the most useful development knowledge will be the gems you find through research.
Kshitij Sinha
3,186 PointsThanks Ben Jakuben will surely do that.