As some may be aware, I have been putting some of my efforts towards becoming an android developer.  As a .Net developer, I absolutely loathe Eclipse, which is the Google preferred IDE.  The good folks at JetBrains have updated their IntelliJ IDEA IDE about a year ago to work natively with the Android SDK.  As a .Net developer, this is awesome! Anyway, one of the struggles I have had is getting my Android APK to use the proguard configuration from IntelliJ, which kind of isn't good since it's use is recommended prior to deploying an application.  Well... today I figured out how to make this whole thing work. Step 1: Update local.properties My build script kept failing because the SDK path was wrong.  I use Linux as my principal Android developer machine, and the path in local.properties was incorrect.  It was basically missing an x in the path, but once I updated it, it worked like a charm. Previous...

So last night I gave a presentation on In-App Billing using the Android SDK at the St. Louis Mobile Development User Group (hosted at Asynchrony).  This was a first for me, as I have only presented on .Net or DotNetNuke topics at the St. Louis .Net User Group or St. Louis DotNetNuke User Group meetings. All in all, it went very well.  I surprised myself by actually knowing the topic fairly well, and the questions posed by the attendees were pretty answerable.  The presentation itself (which will be posted soon) covered: why Google provides an interface for In-App Billing, and not an interface for In-App Purchasing the business and technical requirements for developing against the service some pointers on testing...

A frustrating problem with a simple solution for custom module development using resource files.