BlackBerry Playbook - The Good, The Bad, and The Ugly

I finally got to test the released version of the RIM BlackBerry PlayBook and here are my impressions of the PlayBook - the good, the bad and the ugly.

The Good

The PlayBook is a 7 inch tablet device with a new operating system by RIM. I am a fan of the 7 in format as I already determined when I  tested the Samsung Galaxy. The 7 inch format is big enough to get a decent browser experience and to be able to type and yet it makes the device immensely more portable. The device has two cameras and an HDMI slot, although I didn’t find any SD card slot to my disappointment.

The PlayBook has a very sharp looking display. The resolution is 1024x600 which is more dpi than the iPad with 1024x768 given its smaller screen size. I like the user interface of the new PlayBook OS (QNX) which makes the app interaction very easy - it is much more obvious about which apps are currently running compared to the iPad. Talking about the UI, I have to mention the Flash support which is something iPad doesn’t do. That said, I am not so sure lately I really want Flash to survive, given the abundance of invasive Flash adds. I do realize though that the advertisers will find another technology to annoy me with their ads if they don’t have Flash.

The PlayBook user interface is awesome

Finally, I like the standard set of applications that come with the PlayBook. Besides the usual suspects such as browser, music player, picture viewer etc., the PlayBook also comes with a set of office applications called Word To Go, Sheet To Go, and Slideshow To Go. I’ve tried to open up a couple of Office documents and I was positively surprised to see a pretty decent fidelity of a PowerPoint deck - something the Keynote app on the iPad still struggles with. That said, don’t expect to be able to use a complex Excel spreadsheet with pivot tables.

The Bad

There were a few things I didn’t like about the PlayBook. First, the device is surprisingly heavy. With 425 g, the device is too heavy to hold comfortably in one hand for a long time - i.e. when reading a book. The iPad weighs 607 g which is much more but given its size, the weight is not that surprising. The Samsung Galaxy weighs 385 g which is less but even that was too much for reading when I tested it. The Kindle only weight 241 g which is why it is such a successful reading device.

I was impressed by the fidelity of PowerPoint decks opened on the PlayBook's native Slides To Go app.

Many people have reported about the hard to use power switch. It is really, really hard to engage - the designers clearly haven’t tried the button themselves. That said, you don’t need the power button much - a simple sweep on the screen wakes up the PlayBook from hibernation. I did like the volume buttons that some of the reviews criticized. My iPhone and iPad have them too and I use them all the time.

While the PlayBook hardware appears very slick, the software was clearly a bit rushed. The PlayBook has no native calendar or email client. To use email, the PlayBook has to be tethered to a BlackBerry (smartphone) via a bluetooth connection which I wasn’t able to test since I traded my BlackBerry in for an iPhone not long ago. This limitation will likely go away in some future update but right now, the tablet’s usefulness is limited without email which is my number one application on the iPad.

The Ugly

In the end, it is all about the software - most notably the apps. And that’s where the PlayBook has its work cut out. The BlackBerry has been only slowly trying to catch up with Apple and Google in apps availability but the PlayBook OS (NQX) is distinct from BlackBerry and there are only a handful of apps available. While the PlayBook has in theory most of the apps one would need for work - let’s ignore that email issue for a minute - the fun apps are in very short supply. From the list of my most useful iPad apps, I was able to find a browser, a basic RSS reader, a note-taking tool, Twitter client, and I’ll throw in a Facebook client which iPad doesn’t have. From the list of my coolest iPad apps, I didn’t find a single one.

The Trump Card

The key to the PlayBook’s success will be RIM’s ability to attract developers. Right now, I am a bit skeptical. However, there have been some reports about the PlayBook’s ability to support Android apps in the near future. Should that come true - and should the apps run in a realistic mode with full capabilities - RIM might pull a great coup and address the lack-of-apps issue overnight. But until that happens, the PlayBook’s outlook is questionable.

My son is testing the 'play' part of PlayBook. He enjoyed the Flash support.

The Summary

The PlayBook is a beautiful, well designed device.  Assuming the apps will become no issue, it will be a solid option for many users, particularly those using it primarily for business. Besides the native office apps, PlayBook also leverages RIM’s security infrastructure and offers a much more secure option than Google or Apple. But the apps are a major issue today and with pricing on par with iPad ($599 for a 32 GB version), the PlayBook is hard to justify in comparison to the iPad.

OpenText Is Everywhere - Even On a PlayBook

OpenText announced a new release of Everywhere last week at Content World. And since there was a lot of buzz about a lot of things at Content World, I want to add a few thoughts and comments about this mobility announcement. No, I won't talk about the usual features and benefits of mobile applications. Instead, I took a look under the hood of the product.

This is the second product release of OpenText Everywhere. Its primary focus is on expanding the capabilities that expose the functionality of the underlying ECM Suite with focus on process automation, social interactions, and content access. It is also adding support for Apple’s iPhone and iPad devices, alongside the previously provided support for RIM’s BlackBerry. And in his keynote, OpenText’s CTO Eugene Roman demonstrated an early version of OpenText Everywhere running on RIM’s PlayBook. That was apparently the first time the PlayBook has been shown outside of keynotes delivered by a RIM executive. Yes, OpenText and RIM are both headquartered in Waterloo and so there is an obvious connection there. (Note: The support for Playbook has not been formally announced yet but rather eluded to in a fairly public forum).


The thing that makes Everywhere distinctive is its design. Instead of trying to be a mobile rendition of an existing desktop application, it has been designed natively as a mobile enterprise application. Here are some examples of what makes it enterprise-ready:

- Bandwidth-Management: Managing bandwidth utilization is critical and not just because of performance. Bandwidth on a mobile device costs money. And when you are on international roaming, it costs a lot of money. To avoid spiraling communication costs, the mobile applications has to be designed as much less “chatty” – something that is often not a big concern for desktop applications. When accessing a 20 MB PowerPoint presentation, you don’t really want the file downloaded to your iPhone – the roaming charges could be excessive. OpenText Everywhere solves it by converting the presentation on the server-side into a set of images rendered on the fly. OpenText owns this rendition technology since the 2008 acquisition of Spicer and this technology is now embedded into the OpenText Everywhere application.

- Connectivity: Many of my iPad applications are useless if I don’t have any connection. All I get is an error message which might be OK for a free consumer application but an enterprise application needs to be productive even if when I am on a plane with no connectivity at all. OpenText Everywhere makes this possible to work offline and it queues up my activities for when I reconnect. In addition, Everywhere allows to be configured to work over Wi-Fi or 3G to better manage my connectivity.

- Security: Security is paramount for enterprise applications and it is a major concern for mobile devices accessing your confidential data. Today, IT has to support a multitude of devices with different security capabilities while some are corporate while others are employee owned. OpenText Everywhere leverages the existing security infrastructure of the device for encryption and the ability to wipe clean a lost device. This is much easier with BlackBerry than with other devices but that will be the topic of a future blog post. OpenText Everywhere has been also designed to support existing security policies such as use of a directory-based authentication and the leverage of the highly secure and compliant infrastructure provided by the ECM Suite.

- Usability: A mobile enterprise application cannot be just a scaled down version of a desktop application. To gain user acceptance, the applications need to be designed specifically for the mobile device and ideally leverage functionality of the application the employees use regularly. That means it must not attempt to squeeze the same amount of information and the same number of buttons on each screen. To do this, OpenText Everywhere has been designed with the device in mind and it takes advantage of the unique facilities of each device (e.g. touch screen vs keyboard) and push notifications – again, these concepts don’t really exist on the desktop. As a result, for example the Everywhere screens for search results and ‘my assignments’ list look and behave differently than on desktop – they are optimized for the task at hand and for the device.

I see more and more of my co-workers using mobile devices as their default tool. While mobile enterprise applications are still in their infancy, I expect that the mobile interface will be the default user interface in the not too distant future.