This is the first of a multi-part series on how I developed and deployed an Android app for the Triangle .NET User Group (TRINUG). I’m not an Android developer and haven’t touched Java in over 10 years. What was my solution? It was a mobile-targeted HTML5 web site turned in to a native app using PhoneGap Build.
The PhoneGap Build ‘Getting Started’ document serves as a great introduction to what PhoneGap Build does:
PhoneGap Build is a service that allows the developer of a mobile-based web site to zip up the site’s assets, upload them, and then return installable app files for various mobile platforms. This allows a single code base to run on iOS, Android, Windows Phone, etc. It is in effect putting a wrapper around your web site to make it installable to the various mobile platforms it supports.
I thought it would be best to break up the story of my experience in a series of blog posts outlining the logical steps of the development process. I’ll start with developing the site and describe the design considerations I had to contend with. Next, I’ll detail the PhoneGap Build process which included getting my source code up to the build service and obtaining the desired output. Testing and debugging is very possible, and even powerful when using PhoneGap Build so I’ll be covering that. I’ll then detail my experiences with submitting the app to the Google Play marketplace. Finally, I’ll summarize my thoughts on the PhoneGap Build process and discuss what I believe to be the future of this approach to app development. I’ve put together an outline of this series of posts: