Apart from the obvious of starting your own app from scratch, you could try searching for an open source Android project and fix some bugs or add a feature.
Andrew On 15 May 2011 11:19, "Adam Ratana" <adam.rat...@gmail.com> wrote: > This is a great thread. I'd like to add to the below points: > > - do something in a domain you know well and enjoy, that will touch on > various areas of the android platform > - solve an interesting problem in that domain that android/mobile/etc may be > uniquely suitable for > - set some limits on what your "version 1.0" will be > - dive deep into it... you're subscribed to this group and there's a wealth > of knowledge here in the archives and among the braintrust that reply to > intelligent questions and topics -- literally, the google engineers who > write the SDK respond to pertinent threads! > - sleep less, sacrifice some time to learn as much as you can, really, > _sleep less_! > - make lots of mistakes, fail, do things the wrong way and then improve > - publish > - have fun, experience some joy and passion for the process, it's an end in > itself! > > After you make your first app, you'll be in a much better position to get > android work, as you'll have something to show for your general development > skills, in an android product you've produced. > > On Saturday, May 14, 2011 12:25:17 AM UTC-4, Brill Pappin wrote: >> >> haha, particularly since 25 years ago, hardly anyone knew java (if it was >> even released). >> I have something between 15 or 16 years of experience with java now now >> (exact numbers are fuzzy in my old age)... and I started with java 1.1 :) >> In fact i think its only about 17 years old! >> >> Anyway. >> If your writing code for someone else, there are multiple ways that can >> work, but demonstrating an published app should be pretty good proof. >> >> Our group decided to publish apps ourselves because we wanted some that >> didn't exist or we were not satisfied with what we could get. >> Even with four apps in the market, it doesn't pay us nearly enough to >> replace our day jobs... so we work at night and use the money we make to >> support our customers and buy hardware when we want it (or to finance some >> other startup project idea). >> >> I personally also get to develop on the Android platform for my clients >> (the ones where I actually make my living) but its a side thing, simply one >> of the many many skills I'm expected to have or to able to handle in order >> to get a large hourly rate. >> >> The long and the short of it is. Start. >> or i guess if your a nike fan. Just Do It. >> With luck you'll get an opportunity, and when you do you will have >> something to show for it. >> >> You are lucky in that right now Android developers are in short supply so >> your more likely to land a job doing it with minimal experience than you >> will be later. Personally, I'll never go back to a cubical farm if I can >> help it, but its taken years to get to that stage. >> >> > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
