So by now you’ve probably heard about the Nexus 7. We heard it was coming last week, and now after using it for a few days, here’s my review.
As a backstory, you should know that prior to recieving the Nexus 7 at Google IO, I already owned a Motorola Xoom, a Samsung Galaxy 10.1 (from IO 2011), and an HP Touchpad. Surprising as it might seem for someone with all these gadgets, I actually don’t really get tablets. I have a laptop, and a smartphone, and there just really isn’t a whole lot of use for a tablet that I’ve found. I’ve tried them all, including the iPad, and I just haven’t found a way to fit it into the collection of things I use on a daily basis.
But, I don’t give up trying so easily. Nor has Google it seems, because slowly but surely, Google has finally put together a combination of software and hardware that is an absolute pleasure to use. Not only that, but at $200, it’s a steal compared to other popular options.
The best way to review the Nexus however, is by breaking it down into the two main components that it’s comprised of: software and hardware.
The core of the Nexus 7 is Android 4.1, codenamed “Jelly Bean”. Jelly Bean was not a revolutionary update like its predessesor, Ice Cream Sandwich, but an evolutionary one. It includes three main changes, as well as some small ones. The main changes were “Project Butter”, Google Search, and Google Now.
Project Butter has probably made the most significant impact for me on the overall feel of Android. Prior to IO, my main complaint with Android was how occasionally laggy it was. However, in Jelly Bean, Google has smoothed out the experience with faster response to touch, animations, and even has the CPU ramp up faster as a response to touch events. Speaking of touch events, Google has apparently devised a way to predict where your fingers will be, and allows the system to respond more quickly as a result. The sum of these changes results in a much smoother feel to the entire operating system.
Google’s new voice search is their strike back against Siri. Powered by Google’s Knowledge Graph, it can do a lot more than Apple’s offering.
The speech-to-text seems to be significantly more accurate than Apple’s, as well as much quicker. I imagine this is because Google has moved the speech-to-text engine onto the device, as this is another feature of the new keyboard (more on that below).
Instead of just listing off a whole bunch of things that I’ve tried, here’s a video from JLishere, who has compiled 41 queries against knoweledge graph. He demonstrates the wide variety of what Knowledge Graph allows the device to respond to, like local queries, transit directions, and what seems to just be tidbits from Wikipedia.
What’s most interesting to me, however, is the preview of the possibile ability to access core hardware functions, like turning on and off Wifi or Bluetooth. Another interesting feature is how this new voice search seems to fit in well with another new platform feature: Google Now.
Google Now is a new card based system introduced in the new version of Android. It tells you about the weather, traffic information, sports scores, and other tidbits of information you’re likely to look up during your day. It’s quite convenient to have information about an upcoming flight available without having to keep checking it, or traffic information regarding my daily commute delivered right to my handset or tablet. Right now the number of available ‘cards’ is limited, but as the number of uses expands, the functionality will continue to grow.
In addition to the fancy speech-to-text features, as well as the speed improvements, Google has added rich notifications that allow you to perform actions without opening the app. You can control the music player, or reply to a SMS message, all from the notification tray. Another addition is a new keyboard, which does text prediction. If you’ve ever used Swiftkey, you’ll feel right at home with the new stock keyboard. Also included is the offline speech-to-text engine, which allows for speedy transcription, if you’re into that.
Other changes include some fancy new camera and gallery improvements, and now Chrome is the standard browser. Combined with tab sync from other machines, this is the best mobile browsing experience I’ve had so far.
At 340 grams (compared to the Kindle Fire’s 413 grams), the Nexus 7 feels extremely light. It measures 10.45mm thick, which is just shy of the thickness of the Kindle Fire. The front of the tablet is an IPS 7-inch 1280 x 800 display, which is powered by an NVIDIA Tegra 3 quad-core processor, with 12 GPU cores, and 1GB of RAM. As for storage, it comes in 8GB ($199) and 16GB ($249) capacities.
In addition to that serious computing power, the Nexus 7 has plenty of sensors and radios. Under the hood, there’s Bluetooth and NFC, not to mention GPS, an accelerometer, a digital compass and a gyroscope. All this is paired with a battery that managed to last me around eight hours. Based on other reviews I’ve seen, the battery seems to last between seven and nine hours, depending on usage.
This all sounds fantastic, but there’s a few things that could have been added/improved as well. First, since there’s a lack of a rear camera, no camera app has been included. This is most certainly not a deal breaker, but it’s worth noting, if you’re into self portraits. There’s also no HDMI/MHL output, nor a MicroSD slot. The only other gripe that I have is that the speakers are fairly inadiquite, so you’ll be reaching for your headphones.
The Nexus 7 is a great deal for a tablet that costs just under $200. It has a great display, smooth performance and all the bells and whistles of Jelly Bean. In my opinion, this is the best Android tablet available.
And for the first time, I’m actually excited about using a tablet.
Oh yeah, if you were wondering: I did preorder Project Glass.