The Winston Group is a strategy and research firm dedicated to making ideas matter.

Tech: Five ways Keynote for the iPad badly misses the mark

by canderson

Because we at The Winston Group heavily use Apple’s presentation software called Keynote, we were very excited when a version was announced for Apple’s new tablet computer, the iPad. Sadly, our expectations haven’t been met.

I just wrote a long post on “The Unofficial Apple Weblog” detailing the five ways in which Keynote for the iPad misses the mark. Check it out!

One app that I (along with a growing contingent online) am incredibly disappointed with is produced by the one company who shouldn’t need more time to learn the device — Apple, Inc. I’m referring to Keynote, Apple’s presentation application. Keynote for the iPad was billed as a full-featured presentation package, offering the same features and full compatibility with the wonderful desktop version. As a Keynote addict, I was incredibly excited to see how this program would be redefined by a giant touch screen. 

After using the app since launch day, I’m sad to report that Apple has made some big mistakes with the iPad version of Keynote. I’ve noticed what many concerned and angry commenters on Apple’s support forums have also noticed: the iPad corrupts and changes many Keynote presentations imported from a Mac, lacks support for custom fonts, and overall is a stripped down version of its desktop relative. I was frustrated to experience these problems because I had been so excited for the iPad’s Keynote potential.

Ars Technica: iPhone and Snow Leopard Server’s failure to communicate

by canderson

Ars TechnicaCheck out Chris Anderson’s article in Ars Technica about iPhone and Snow Leopard Server’s compatibility problems. We’re excited for Chris, as it’s his first published tech article!

With Apple pushing the iPhone as a full-featured smartphone for the enterprise, you’d think it would work perfectly with its own enterprise-focused Snow Leopard Server. You’d be wrong. The iPhone even functions better in an Exchange environment.

Read at Ars Technica