Once you've developed a working application with PhoneGap, the next challenge to overcome is taking that code to the next platform of choice. One way to do it is to create a new development environment for each platform, but another way is to use the PhoneGap:Build service to build the cross-platform binaries for you.
The easiest way to get started is to create an account at PhoneGap:Build, start the new app process, and upload your application as an archive or pull it from a git repository.
Now go make a cup of coffee/tea, and wait for the compiling to complete. When done, the following formats are available to download:
Because I have not linked my PhoneGap:Build account with an Apple developer account's signing credentials, the iOS application has not been built.
I have a toy Android application that I've been working on as a follow-up to a previous article on setting up an Android/PhoneGap development environment; I put it up on the site as my one free private app and installed it on Symbian.
Much to my surprise, the application loaded and sort-of works. It's not without rendering bugs that I haven't debugged, because it is Symbian; and while its no shock to see that the functionality of the speech-to-text and text-to-speech libraries that I made use of in Android is missing, the fact that it didn't crash the application is good.
There is also an API available to automate the process of uploading, building, and downloading applications.
If you have a simple PhoneGap app and you want to go cross-platform, there's a chance that PhoneGap:Build could work for you in production, but I'd be genuinely surprised if it did.
For an experience where, for minimal effort, a working package is returned in rapid time, it's hard to go past the service as a tool that lets a developer know how their application functions on a particular platform, and where the gaps in it lie.
Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining the company as a programmer.Leaving CBS Interactive in 2010 to follow his deep desire to study the snowdrifts and culinary delights of Canada, Chris based himself in Vancouver and paid for his new snowboarding and poutine cravings as a programmer for a lifestyle gaming startup.Chris returns to CBS in 2011 as the Editor of TechRepublic Australia determined to meld together his programming and journalistic tendencies once and for all.In his free time, Chris is often seen yelling at different operating systems for their own unique failures, avoiding the dreaded tech support calls from relatives, and conducting extensive studies of internets — he claims he once read an entire one.