Playing with iPad

Unfortunately we don't have an iPad yet (Apple, Mr Steve! can we have one please???) but, what we do have is the beta of the new SDK for iPad development. And.... it's beautiful.

We are of course under an NDA regarding new features so I cannot say much. However, I do think I am able to share the following with you.

The iPad is of course (at its most simplistic) a giant iPhone device, although the larger screen and improvements/additional features Apple are providing allow for much richer software experiences and usability for a lot of applications that could never function properly on an iPhone. This is mainly down to the physical size and the resolution of the screen you have to work with. That sounds obvious, and it is. 'Serious work' on a display the size of the iPhone's is difficult. The iPad make it not only feasible, but also useable, and in many cases, probably pretty enjoyable. That is massively important.

One thing that I'm sure you can understand Apple are likely to encourage with the iPad is the way applications adapt themselves to the physical handling of the device by its users. Many iPhone apps only run in a portrait mode because it is more useable for viewing lists of information or data entry and more often than not offers a better user experience for non-media content than landscape views do. This is mostly negated with the iPad because of the high resolution. In practice, for the first time with an iPhone OS device, you can have landscape views that are more useful than their portrait cousins for all kinds of applications. Showing more information and alternative information in a useful manor. I'd suggest that all iPad applications (except maybe games) should work in whatever orientation the user is holding the device in, and give the power back to the user.

Porting an existing iPhone app to the iPad can be either a relatively simple task, or a more complicated task - depending upon what the app is and what resources it contains and needs to work with (especially image resources e.t.c. which must be provided in much higher resolutions). This is mostly obvious because of the massive difference in the physical resolutions of the displays. The iPad does allow you to run existing iPhone apps natively at either their original size (smaller rectangle in the middle of the iPad screen), or zoomed in to fill the iPad's screen. This does not automatically gain you any advantage in terms of the actual screen space you have to work with because you are ultimately just looking at exactly the same as you would be on an iPhone.

iPhone apps which consist mainly of table views and lists of information (which so many do) are far easier and more efficient to port to the iPad. Other apps will likely require much tweaking, additional resource provision/creation and even more thought because you now have an iPhone OS device which is close to the screen size offered by your laptop. That's much more than a phone and you need a different mindset when thinking of the possibilities.

With some of our current 'play time', I have ported most of one of our client's apps to the iPad (I won't tell you what app it is because they don't know yet and now isn't the time!). As it's largely a data entry app, the process was more trivial than most ports are likely to be, but there is still much to do in terms of images used and the original assumption of an iPhone's 320x480 pixel display when designing, preparing and developing the app.

Whilst I have a few personal doubts about whether many people will feel an absolute need to own a product that fits neatly between their iPhone and MacBook/PC laptop, there is no doubt that the iPad is a lovely thing - and I'm sure anybody with an income that allows them to purchase a lot of new shiny things will be snapping one up. We're looking forward to getting our hands on a real iPad ASAP (whether Apple or Mr Jobs send us a freebie or not remains to be seen - come on Steve, go on..... you know it makes sense).