Team Buzztouch, I have customized Android 1.4 code in a lot of different places to handle different situations. Some of the features that I have added will only run on Android 2.1 and up. Do you know if you are going to 'try' to duplicate all the features from iOS to Android like the 1.4 code. Or is there going to Be features that are specific to iOS and or Android? A hard sticking point is more code will have to go into the webview for android vs iOS.. I am working on that now. Such as being able to view HTML5 videos in a webview, geo location and so on.. Just wondering where you all are at with it... Thanks...

The goal is to not have features that are only supported on some devices and not others. Part of the delay with Android is that the updates to their OS are changing faster than we can keep up with. Funny. At this point it looks like buzztouch v1.5 for Android will require 2.1 and up. Like you mentioned, the webview for Android is a nightmare (compared to iOS) but should work when done. The biggest hang up on our end are all the transition options for each screen type. The transition types available in the buzztouch control panel are ios-centric but it's important to us to get them to work if a user decides to use them for Android. We don't recommend a bunch of wild transitions but do understand the need for flexibility. So, we continue to plug-away as we inch-by-inch crawl on this thing. Sucks...but...we'll get there.

@Zoid66 Have you been successful getting webview to properly render HTML5 videos in a webview? If so would you care to do a code exchange with me? @David@buzztouch Developers can always build their app setting their Project Build Target to 7 or higher and then setting their SDK version availability as shown below: <uses-sdk android:minSdkVersion=5 android:targetSdkVersion=9 />

Great tip about setting the sdk version, should work. Coding away...java drives me insane! LOL