The other day I stumbled on a Make Use Of article about buzztouch, a "iPhone, iPad, Android app builder and content management system."ﾠ Since we're researching options for creating cross-platform mobile applications, and the article indictated that it was worth checking out, I decided to sign up and give buzztouch a spin.
Once you've created the app, you can then download the native source code for the app:ﾠ you're provided with separated source code downloads for IOS and for Android.ﾠ The source code comes in a .zip file, which also contains a readme file with instructions on how to compile the source code for that particular platform and create the native app.ﾠ It only took me a few minutes to create an Android app from the source code, and it only took me that long because I had to provide a Google Maps API key to enable the mapping component I'd added (the readme provided exact instructions on the changes I need to make it the code to use the key).ﾠ I had my IOS developer colleague compile the IOS version of the app, and it was also smooth sailing for him.ﾠ The resulting app on the Android platform looked a little rough simply because of the generic design elements, but the IOS version looked pitch-perfect.
The first time you access any component or screen in the mobile app, there is a pause as the app retrieves the content or content instructions from buzztouch then caches it for local use.ﾠ This is where the content management system aspect of buzztouch kicks in:ﾠ any changes you make to the app on the buzztouch site get pushed to (or pulled by, not sure which) the mobile app.ﾠ So the app owner doesn't need to recompile and update the app through the App Store or the Android Market in order to make content changes.ﾠ If the mobile device doesn't have a network connection, then the cached content is used.
So what's my overall take on buzztouch?ﾠ I think that if you need to build a mostly informational mobile app, something that serves the same purpose as a mobile-optimized website, then buzztouch is a compelling option because of how easy it is to create the app and then update the content.ﾠ Even if your long-term strategy is to redesign an existing "desktop"-optimized website to be mobile-friendly as well, a buzztouch app could fill the void until that goal was reached.
If you need to build a mobile app that's more interactive, one where the user can send and receive custom data, then buzztouch is at best an incomplete solution.ﾠ There are no buzztouch components for collecting data (though the app itself will capture GPS info from the device in order to map where the app has been used, which is both useful and slightly disturbing), but you could probably use the Custom HTML component to create a web form that transmitted data via a regular form submit or via AJAX.ﾠ And there are as yet no components that let you access device-specific functions like the camera or accelerometer.
On the other hand, if you are capable of doing some IOS or Android coding, the native code provided by buzztouch could serve as a starting point for adding additional functionality:ﾠ the buzztouch folks seem to be open to folks using the generated code to advance their learning of native app programming.
So overall, I'm impressed with what buzztouch has done so far with the direction they've taken, and I hope they continue to improve on the platform.