Android Technical Article writing

Several weeks ago I applied for an Android Instructor position. During that process I prepared rough drafts of materials covering these Android Programmign areas:

Android WebView Web Programming Using Google Web Toolkit

Android 2D OpenGL Game Programming

Android Advanced Agile Techniques

Android Advanced Programming Replacing Default  Applications

Android Game Programming using the Simple Framework

Obviously, the Android WebView Web Programming Using GWT was the most complete one. Obviously, if Apress approves that one I should turn in another book proposal in late October or November. Obviously, the game areas would be the most popular area since OpenGL in Android 1.6 is now entirely fixed. Certainly, Game Programming Using the Simple Framework may be more appealing with the project handset sale sin q4-09 and q1-10 as its basically using the basic computer language to put together the Android Components like Lego blocks into a functional game.

But, I do not have to make that decision until after Apress approves the Android WebView Web Programming Using GWT Book Proposal and than not until possibly November. And on top of that I have my set of Mock Test Object classes to finish and process through the Android Project Code approval process. It will be an interesting set of months.

Advertisement

Android Webivew Programming using Google Web Toolkit

Image via CrunchBase

It might get interesting in the next few weeks. I am reconsidering completing a book proposal for Android Webview Programming using Google Web Toolkit. It is a publishing company I trust while the advance is low the other opportunities that it could produce are somewhat bigger. Some of my online firends/peers have also authored programming books for this publisher.

Android and Google GWT

Now I have an integration decision with AndCooper Android Java Application ANT based build tool. With the webview web code suport in the build tool my diea was at some point to swtitch to Goolge GWT compiler support and keep the non GWT  web tooling support there for those who wil not use Google GWT. The key question is do I make a separate project just for GWT and feed it in or a new set of directories and ANt script code to support GWT JS  generation in the main Android project.

Seems to me that is should be part of the overall Android Project structure and plus if I were say secretly working on a an Android application using Motorola CLiQ-Motorola Blur APIs and the Google Maps APIs it would seem that the Google GWT tooling would be an ideal component in that development work-flow.