I seem to stuck at creating a complete application even after reading a few books on Android.
That wasn't the case when I first did PHP 10 years ago, after reading 2 or 3 books, I managed to grasp the idea behind, start making database interactive scripts with very minimal referencing to the books.
Android seems like a giant beast which is hard to handle. If I were to make an app with map function, I can't write more than 5 lines without reading the books. When I wanted to create another app with telephony function, I would "copy" the codes from books and modified from there. After learning for 2-3 months, I still couldn't remember the programmatical ways how to handle ListActivity. There seem to be a few thousands of classes that I need to remember. And till now I still not knowing the reason to use "this" as context, I just figure to use it when context was needed, if not getApplicationContext() would be a good replacement. The thing is, 99% when context was used, it must be a call of "this" from current activity, why couldn't Android framework handle the context internally and do developers a huge favour and let the 1% call it with extra arguments when it's really needed?
When I did PHP, I spent 25% of the time on script planning and overflow. 70% on writing the code. 5% on referring the syntax.
Now as I do Android development, 5% time needed on planning (because most of the apps look very straightforward with minimal purposes), 50% time copying the codes (from books or online sources), 10% time modifying the codes, 35% troubleshooting where the code went wrong. My job is basically one thing - blending all 'tiny recipes' into a working condition.
Was it just me, or most developers stumbled into the same problem?