The BlackBerry PlayBook Review
by Anand Lal Shimpi on April 13, 2011 9:00 PM EST- Posted in
- Tablets
- Smartphones
- RIM
- BlackBerry
- PlayBook
- Mobile
Camera
The PlayBook comes equipped with a 3MP front-facing camera and a 5MP rear-facing camera. Neither sensor is aided by any sort of Flash. The rear sensor is 4:3 and captures at 2592 x 1944 for full resolution. By default the PlayBook shoots in 16:9 which results in a cropped 2592 x 1456 (3.7MP) image.
Image captures from the rear sensor are high contrast but typically lack sharpness. I've also noticed that it's not too difficult to trip up the white balance algorithm, at least outdoors.
RIM takes a page from Apple's playbook and bumps up the contrast to make up for inherent limitations in the camera sensor.
The front camera also has a 4:3 ratio sensor, capturing natively at 2048 x 1536 (3MP). In 16:9 mode you just lose some vertical resolution as the sensor is cropped to 2048 x 1152 (2.35MP).
The front facing sensor is unusually good indoors without a lot of light. You still can't take photos in pitch black but with a little bit of ambient light you can generally get a pretty bright image out of the front facing camera. RIM will eventually enable video calling between PlayBook users, however it's not functional on the review build of the PlayBook software.
The camera app itself takes about 3 - 4 seconds to start and has a pretty simple UI. There's a button to switch between stills and video recording, a slider for digital zoom, a shutter release button, a location toggle and a button to switch between front and rear facing cameras.
It takes about two seconds to switch from the rear to the front facing camera, and about 1.8 seconds to capture an image. While it may not sound like a lot, the capture latency is high enough that you have to make sure you hold the PlayBook still for those 1.8 seconds otherwise you'll end up with a shifted image.
The camera app supports minimal customization. You can change aspect ratio, turn on image stabilization and choose either auto, sports or whiteboard for camera presets.
Videos
Both the front and rear sensors can shoot video at 480p, 720p or 1080p at 30 fps. Videos are shot at 720p by default.
Captured video actually doesn't look too bad. The lack of sharpness I complained about in the stills is somewhat masked by motion and what we get instead is a pretty reasonable platform for shooting video, at least for sharing on the web.
Facebook
Twitter
RSS
77 Comments
View All Comments
Andrew911tt - Thursday, April 14, 2011 - link
You have the Xoom at a price of $799 but you can get the 32 GB wifi version for $599http://www.amazon.com/MOTOROLA-XOOM-Android-Tablet...
MTN Ranger - Thursday, April 14, 2011 - link
Excuse my off topic question.Anand, I notice you use Lafayette Village in your videos a lot. Do you live/work near there? We enjoy having drinks at the Village Grill and my wife loves the Upper Crust Bakery. I have taken photos there and think the architecture is great.
Anand Lal Shimpi - Thursday, April 14, 2011 - link
I'm not too far from there. It's the most interesting thing that I can photograph quickly outside of my dogs playing :)Take care,
Anand
jensend - Thursday, April 14, 2011 - link
I'm serious- this is probably the best commercial OS out there. Of course, these days most people judge an OS mostly by its included applications and the collection of software written for it, which doesn't look so good for QNX, but as far as the actual OS is concerned QNX is extremely well designed.baba264 - Friday, April 15, 2011 - link
I would tend to agree.I was very impressed upon reading all the nice features that this OS has and that are still lacking in mainstream PC OS.
The the tight kernel, the sandboxing, the thread management, the corruption protection all of it sounded real nice. Of course since it wasn't the focus of the article, many question remain, especially performance wise, still it sounded like an impressive work.
vision33r - Friday, April 15, 2011 - link
Because people are used to the iPhone / iPad and App Store being the standard.QNX is a good OS, it is tight and lean. There won't be a fragmentation problem like Android has.
The only problem is that RIM will restrict the device's functionality so that it cannot replace a Blackberry device and risk losing lucrative smartphone sales.
B3an - Friday, April 15, 2011 - link
"You can't really hover to expose controls with a touchscreen so what you end up doing is a lot of quick tapping to try and bring up controls, change the setting you want and get back to playing the video. It's frustrating and doesn't work all of the time. None of this is RIM's fault, but now that tablets are at the point where they can start to behave like notebook/desktops web developers will have to rethink the way they build websites. "I'm a web designer and specialise in interactive websites and apps, but touch screens have the ability to hold this area back and make it less elegant/messy for other devices with no touch.
The problem is not with web sites designed for non-touch devices but the need for a touch device to support hover in some way. For instance this could be done if a touch screen could detect a finger hovering over an area of the screen within say half an inch of the screen surface. That could work well if done right.
As sites get more interactive and advanced hover controls in the UI make more and more sense. because of interface complexity rises and the need for more buttons and stuff all over the place.
The thing with Flash is that being as it's far more capable than HTML5 for interaction (and with pretty much anything else too) is that it's Flash that is more likely to use hover controls in some form. But some HTML5 things are stating to use it, like the default skinned Chrome HTML5 video player for instance. Hover just makes perfect sense for certain things and touch screens need to fix this, not us web designers.
ElementFire - Friday, April 15, 2011 - link
This is a seriously well-wrought review. I'm especially glad you dedicated an entire section to Bridge, and addressed the free tethering question. As you stated, this is huge (assuming the carriers permit it), as it's the closest thing to truly unlimited browsing data plans (for no additional charge!) as we'll get now.It's a pity that Android apps need to be re-signed by RIM before they'll run. It makes sense from a security perspective (you don't want malicious apps running amok on an enterprise platform), but I'd have preferred if RIM had severely limited Android VM capability and allowed all apps to *try* to run, rather than requiring re-signing; the vast majority of Android app-developers won't have the impetus to resubmit their apps to yet another platform holder.
The last point I wanted to make was video conferencing: it's a serious letdown to only ship with point-to-point video chat (and even then, only between PlayBook owners!). If you're aiming at the enterprise, I'd expect VoIP/SIP capability and the ability to run WebEx natively. Does the PlayBook support any implementation of Java Runtime Environment?
name99 - Saturday, April 16, 2011 - link
"Pretty much no smartphone or tablet we've tested is particularly speedy over WiFi. Even the Motorola Xoom, at the top of our performance chart, manages a meager 36Mbps. Part of this has to do with the fact that all of these devices are power rather than performance optimized and part of it has to do with NAND performance limitations."Is this not simply a reflection that none of these devices use 40MHz wide channels, they all stick to 20MHz wide channels? I'm not certain about this, but given how the numbers cluster, I would bet this is the case.
(And, of course, none of these devices use multiple antennas for wifi.)
The flash has nothing to do with it. iPad flash can write sustained at a little under 20MB/s (ie 160 Mbs/s) and I imagine other tablets have similar specs.
In theory, the most power efficient way to run wifi is to do get your transmissions done as fast as possible --- in other words use 40MHz and multiple antennas and run at the maximum data rate possible. Of course this requires that the chips being used be maximally efficient in their overhead, so that essentially all power is being burned in RF transmit, not in the receivers, the decode logic and so on. It may well be that the chips supporting 40MHz, let alone MIMO, simply haven't been around for long enough to have their power usage tuned to where the 20MHz chips are.
tipoo - Sunday, April 17, 2011 - link
Most routers and laptops will default to 20MHz anyways.