Trying to evaluate the different ways to publish interactive content to the iPad is, I imagine, a bit like speed dating and you barely have time to assess one method’s better points and its downfalls before you’re being told it’s time to move on in your (vain) attempt to get round the full room. The trouble is, in almost Kafkaesque style, just as soon you begin to feel confident you’re going to get round all the possibilities, you notice another one just sitting down at the end of the table and you realize you’re never going to reach the conclusion. Sooner or later, if you want to get something done, you’re going to have to decide to take a chance and stay where you are, or maybe you should go back four – or should that be five – places.
Though I’d mentioned PhoneGap in my last post, at that time it was only in the corner of my eye and I hadn’t sat down in front of this new arrival and pressed its buttons. I had seen a menu command in Dreamweaver CS5.5 which allowed you to export HTML content to PhoneGap, but an obvious downfall was the need to install the various devices’ SDKs on the local computer – and the iOS SDK is Mac-limited, which ruled out testing on my main computer. What intrigued me most was their completely cloud-based beta service, PhoneGapBuild, and then I saw the announcement that Adobe were buying the company (a bit like PhoneGapBuild subtly telling you it already had other admirers too).