At this point most of the candidates ask "OK, so what else should I know?". I used to give some ad-hoc answer for this question, but it's not the best idea, because I tend to forget to mention about some stuff; and even if I don't miss anything, the candidate probably won't remember half of what I said because of the stress accompanying the job interview.
Anyways, I decided to write down the list of Android learning materials, blogs, libraries, etc. I recommend reading about.
Android basics
Some people's Android knowledge can be summed up as "Activities + AsyncTasks". That's not enough to write anything more complex than Yet Another Twitter Feed app, so if you seriously think of being the Android developer, go to http://developer.android.com/guide/components/index.html and fill the gaps in your education.At the very least you should also know about Fragments and Loaders. If you want to persist the data, I recommend using the ContentProvider. It looks like a hassle to implement at first, but it solves all the issues with communication between Services and UI. While we're at the Services: you should know the difference between the bound Service and started Service, and you should know that most likely all you need is the IntentService. You should also know about BroadcastReceivers, and what is the ordered broadcast and sticky broadcast. Pay attention on what thread the different components operate.
Libraries
Support libraryGuava
ActionBarSherlock
JodaTime
Commons IO
Dagger
Otto
Gson
HoloEverywhere
Blogs
Mark MurphyCyril Mottier
Romain Guy
Roman Nurik
Github
Jake WhartonSquare
Design / UI
Android ViewsAndroid UI Patterns blog
Android Asset Studio
Android cheatsheet for graphic designers
Miscellaneous
Google I/O app sourcesGrepcode
AndroidXRef
I probably forgot about something very important, so please leave the comment if you thing anything is missing.
No comments:
Post a Comment