Today marks an important milestone for me as an Android developer. As I write this introduction to a larger article entitled “My First 30 Android Apps”, I am finishing up the testing phase of today’s app, “Easy Multi Counter”. The publishing of this app marks my 30th app for the Android Market since my first Android App was published June 4th. That’s roughly one every 18 hours. Does this mean I qualify as having completed Dana Hanna’s Software Jedi challenge? (And Similarly Chris Craft’s 30 (Windows) Mobile apps in 30 days and the failed Iphone app-a-day challenge)? There are a number of distinctions in my work that give me pause.

1. I began the challenge as a way to acquaint myself with the Android SDK and (re) learn Java.
2. I don’t work on weekends. That means doubling up apps twice a week to compensate.
3. While all my apps are free, they are advertising supported. I quit my 9-5 grind long ago and advertising (and book sales) pay the bills while I work on my research tech.
4. I’m not stopping at 30. While it may not always be 1 per day, I’m hoping I can push out 100 apps before the end of the summer
5. My code for the apps is not currently open sourced, but I will share any method I have written via email if requested.

As such, I’m actually thinking what I completed was a Software Sith Lord Challenge, primarily due to the monetary gain that comes from releasing ad-supported apps. To put it more formally, I think the “Software Sith Lord” challenge should be stated as follows:
** 30 revenue-generating apps within 30 days time.**

Despite the “evil” moniker, it’s been an exceptionally positive experience for me so far. I’ve met a couple of other interesting Android developers, made a little money, and mocked up a hundred or so potential apps thus far. It’s also a very positive experience day-to-day from a creative standpoint. The act of releasing a fully qualified app daily out into the world is actually the combination of many little creative acts surrounding your code. Drawing icons, writing blog posts and store pages, framing screen-shots and the like all serve to frame your coding experience on the platform as much as any IDE. It’s all quite rewarding when it comes off well. It doesn’t always come off well of course, but that’s what version 1.1 of your app is for.

After the first couple weeks the real limitation is your ability to generate new ideas for apps. As such the best advice I can give (before the mega reflection article coming up) is to mock up (on paper) three or four apps a day, no matter how silly or complex or out of your range they seem. My highest revenue generating app (by twofold) was written in just under an hour, just to prove my cats could hear the ultrasonic ranges Wikipedia said they could. You never know what’ll be popular. Stay tuned for a detailed day-by-day and project-by-project description of lessons learned, advertising revenues, challenges fought, designs and libraries used, and my overall impressions of Android and (re) learning the Java language in my next Article entitled “My first 30 Android Apps”.