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
Samir Doshi
868 PointsNot enough explanation as to "why" in Android tutorials
has anyone else been left scratching their heads doing the android simple app tutorial?
Big challenges I see: 1) the teachers throw a bunch of shit out there and expect us to understand the sequential logic to building constructs without explaining step by step why we one thing after the other in java.
2) the speed ---- slow the heck down guys! - You blast through the most complex subject matter as if we are you... we don't know shit - we have no idea why oncreate goes after layout or what have you - explain it for god's sake! Wow.
It's a very frustrating experience.
2 Answers
Kevin Faust
15,353 PointsI understand your struggle as that is pretty much how I felt when starting android. I'm going to give you my opinion.
I saw your other post asking how much Java one should now before doing android. So i'm assuming you don't know any java. I tried to do the android track before knowing any java. The first few videos in the android track were fine as we didn't really code. We just did some designing and installing android studio. But once programming began to be introduced, I didn't know what we're doing nor why we're doing it. As a result I just quit because I wasn't understanding anything. So I did what you did and asked if we should know java.
The simple answer is yes you should do the java track before android especially if you don't have any object oriented programming experiences. But to be honest you will be just as confused in the java track as java is a mature language and is pretty complex. While doing the java track, I had to ask many questions, search online, etc. I wondered why do I have to go to other sources to find information when I'm paying. But you just have to bear through it. If you're like me, you will be frustrated and want to quit. However if you persist, you will start to understand and get better. Progress might be really slow but it's worth it For each 10-15 minute video in the java track, I spent an additional 1-1.5 hour hours trying to digest the information and find other sources to solidify my understanding.
You don't have to go through the entire java track like I did. You can spend some time on the first 2 sections of the java track. Maybe spend around 2 weeks to really understand how to make objects, classes, etc. Then move on to android. The things we learned in the first few videos in the android track are not things you are expected to know right away even if it feels that way. It took me a real while but just don't give up.
If you have any questions while doing the java/android track, feel free to tag me in questions.
Cheers and good luck,
Kevin
Samir Doshi
868 PointsAwesome advice - I wish this was communicated in some sense in the beginning - like a conditioning statement to the user to prep them and state - take Java.
Kevin Faust
15,353 PointsNo problem and I agree fully.Before I started the android track, I read "success stories" where people with no prior knowledge just jumped into the android track and then after a few months they launched successful apps. Also treehouse promoted the idea that anyone can start android from the get-go. So I assumed I could be like them but well no I couldn't at all. It was pretty misleading to be honest. Before starting android one should suffer a bit from learning java and this will make the whole experience later on much more enjoyable.