Hopefully you decided to write Android applications because you have an idea for an amazing app. If your first ideas are anything like my first ideas, they consist of creating massively multiplayer RPG with real life data simulation where you could fight monsters with your facebook friend contact list, with a dynamic real time networking protocol where you create your own API framework for other games to use and work with your data. In other words, your first ideas are way too complex.
While you maybe on to a ground breaking application, it will definitely take more skill to develop than you have today. The problem with this is, because you are learning so much and trying to get your product out the door, you leave yourself susceptible to burnout; never actually completing anything because you bit off way more than you could chew. Don't get me wrong, some developers do start out huge, swing for the fences and hit a home run. But the majority of us beginners will either strike out or never walk up to the plate at all.
My advice - keep that grand idea that was so good it inspired you take on learning android, and store in the ol' idea bank for when you are fully prepared to execute it. Start out with something simple, something that you think addresses a real problem that a mobile device can handle.
My first application after "Hello World" is a dice simulator application. Something that I knew I could work on that addresses a real problem, not a very prominent problem, but a real problem none the less. Its something I can wrap my mind around and will give me a great introduction to the API. I have some great ideas in the pipe, but you gotta lay the foundation before you build the pantheon.
