Dismayed By Lack of iOS6 Support for the Original iPad

Well, so much for the good intentions of writing more regular but maybe shorter posts for the Apple Harvest. I've been spending most of my time focusing on my mainstream business writing about Business and Software Process Management and actually using Macs and iOS devices rather than writing about them!

After yesterday's WWDC keynote I felt compelled to jot down some thoughts. Like many other users I was looking forward to seeing what Apple were going to offer us, as well as seeing the egg on other commentators' faces when their predictions fell widely short of the mark. Having been passively following the rumour mill for the past few weeks I was pretty much expecting what was announced - and generally I was quite excited.

The new range of MacBook Airs and MacBook Pros look really cool, and by the time I upgrade my MBA (not for a few years I hope!) I think I can be assured that I'm going to get an even better machine. I'm really excited about Mountain Lion and I've already ordered my Thunderbolt to Ethernet connector for my MBA which I'm hoping will have a significant effect on the network spped at the Apple Harvest.

But I'm livid at the discovery that iOS6 will not be available on the original iPad, and only partially effective on the iPhone 4. Apple Harvest readers may remember that I only purchased my iPad 20 months ago so it isn't even two years old yet. But by the iOS6 release date in the autumn, it'll already be obsolete. It's less of an issue for me with the iPhone 4 because I'm already at the end of my contract, and I'll just hang on until the iPhone 5 is available - I would guess to coincide with the iOS6 release later this year.

What I'm most annoyed about is that some of the features should be easily integrated into the 1st generation iPad - specifically the improvements to the Notification System and the Facebook integration. The Do Not Disturb element of iOS6 notifications should be considered an critical omission from the initial implementation and should therefore be available across the board as an iOS5 update release. I am sick and tired of being woken up in the middle of the night by messages flashing up. OK, I could just switch into Airport mode overnight, but I need to remember to do it, and Apple don't exactly make it a one switch operation.

Over the next week I'll research how to jailbreak the iPad and weight up the pros and cons of doing so. I know that some of the annoyances I have generally with the original iPad can be alleviated by jailbreaking so it may be an option. I'll keep you posted on how this progresses in future blog entries.

But for now I'm bitterly disappointed with Apple's decision not to support the iPad 1. I can't see any technical reasons (in the same way that I don't understand why iPhoto for iOS can't run on the 1st generation iPad - actually it can and it does on mine!) because if the 3GS iPhone is supported, the technically superior iPad 1 should certainly be capable.

Maybe, if enough people complain, Apple will have a change of heart, but don't hold your breath. I do intend to write to Tim Cook and Scott Forstall about this, even if it's only to feel as though I've done something positive rather than just whinge - but I think it's a very justifiable whinge!

Snow Leopard - One Week On

Snow Leopard has been running on two of the three machines at the Apple Harvest for a week now, and all is well. Almost.

Certainly there is a general feeling of robustness which is reassuring for critical software such as an operating system. Most of the issues that have surfaced to date are with third party software rather than direct problems brought about through the upgrade.

I documented the issue with Mail and Keychains in my last blog. I'm aware that a number of other people have had similar problems, in particular with MobileMe accounts. My solution of deleting the default keychain and creating a new one appears to have done the trick, but the problem appears to be more insidious on some installations.

I'm more worried about the incompatibility between versions of Mail and its internal databases across Leopard and Snow Leopard, particularly as a mobile user. It used to be a simple matter of copying the \username\Library\Mail folders between machines before and after journeys, but this option will no longer work across machines with different OS. I keep my primary mail store on my iMac at home and copy the mail folders onto my MBP or Hackintosh before going on a trip. This will no longer work with the Hackintosh (until I'm brave enough to try and upgrade it). This will affect anyone who cannot update their mobile machine with Snow Leopard. There are process work arounds to reduce the impact but it is enough to make me consider going back to using Entourage whilst away from home.

My other real gripe is with my printing ability since the upgrade. I use an HP DeskJet 970CXI printer as a workhorse. I have occasion to have to print quite large documents and the 970 has a full duplex facility for double sided printing. HP do not provide drivers for Leopard or Snow Leopard, and users have to rely on the Gutenprint drivers which have proved excellent. Sadly under Snow Leopard, the double sided printing facility is no longer operational, and is likely to remain that way unless the Gutenprint drivers are modified.

This seems to be a very irresponsible attitude from HP, as their response to concerns from users is "buy a new printer". This applies to any printer over 5 years old. So in my case I either have to purchase a new unnecessary printer or double my paper output. Neither option is environmentally friendly, and neither option is likely to appeal to my bank manager.

Of course I could print out everything through the Hackintosh, but if I upgrade that to Snow Leopard I'll fix my mail issue, but lose my printer fix. Nothing is ever simple is it! I wonder if Windows 7 users will have these problems. Well probably not, they'll have a whole different bunch...

The vast majority of my applications seem to function pretty much as normal under 10.6. Notable exceptions are Bento V1 which won't work at all and the majority of system utilities such as Cocktail, Onyx, TechTools Pro. A lot of suppliers beat the gun and released 10.6 compatible versions of their apps prior to the formal Apple release. Most others have messages on their web sites explaining that upgrades are in preparation and will shortly be available.

For a comprehensive and dynamic list of compatible applications check out the Snow Leopard compatibility wiki.