Just one person who want to know something

Angry Birds Rio for Mac os

The success of the Angry Birds game was remarkable, and has launched many versions of this game, be it a PC version, Portable PC version, Angry Birds Rio PC version, or Chrome Web browser version, this time has been also available Angry Birds Rio for Mac OS version.

Is Microsoft Cooking Something to Go Against the Google Glass ?

Everyone has heard about Google Glass, the wearable computer that can be slipped on like a pair of glasses, though it is much more than mere glasses. Undoubtedly the first of its kind, it comes with builtin navigation software that helps you with directions while driving, biking or even walking

Minebea Cool Leaf - Touch Screen Keyboard

Minebea, a Japanese multinational corporationand producer of machinery components and electronics devices, has recently launched its new flat keyboard called as Cool Leaf

Simple shortcuts Windows 7

Might have yet know, on a windows 7 a lot of shortcuts that will help us while working using windows..

Bad Piggies successful as Angry Birds

Bad Piggies, latest games Rovio, are likely to follow the success of Angry Birds and the Amazing Alex. The naughty green pigs is apparently managed to attract the gamers, at least on the iOS device users in the United States (U.S.).

Unordered List

Palm Pre Review

The Palm Pre. It's not just a phone, it's a myth, an idea, possibly a legacy... and a really, really long time coming. It's almost impossible to believe, but the crew at Engadget has been talking about a Linux-based Palm phone since way back in 2004. Through the now-distant years that followed, we were speculating, pontificating, and wishfully-thinking about a new device from a company that we'd come to expect innovation from. But we waited. And waited. And waited. We waited so long, in fact, that we actually penned a lengthy open letter to Palm, pleading for the company to get back on its game. Only when the picture looked really, truly bleak for the folks in Sunnyvale (you know, like $2 a share bleak) did we actually see a spark of hope -- two sparks, in fact -- called the Pre and webOS.

Yes, this is epic stuff. The Pre (and its accompanying operating system) could likely decide the fate of the company largely credited with ushering in the age of the do-everything phone. Since Palm's announcement at CES this year, news surrounding the Pre has been a veritable whirlwind of activity: rumors, half-truths, hate, love, fear-mongering, fanboyism, rampant gadget-lust... and even a little late night celebrity for the pint-sized phone. Finally the time has come to put rubber to road and get into the guts of this thing once and for all. Can the Pre and webOS live up to the hype -- the kind of hype we haven't seen since the launch of the original iPhone -- or do they snap under the pressure? Read on for the full review.

The hardware

Industrial design

In terms of basic industrial design, the Pre is stunning. Palm has gone to great lengths to talk about the feel of the phone, its likeness to a polished stone, how well it sits in your hand, and we'll admit... it does feel pretty great. The shape of the device is distinct, not quite taking a hardline flat-and-square approach of most brick phones, instead exaggerating the curves of the iPhone 3G to their logical conclusion. Closed, the Pre resembles a tiny, extremely glossy black ball. Needless to say, sliding this into and out of a pocket -- even a tight pair of jeans -- is no trouble (though it is a bit chunky around the middle, clocking in at 0.67-inches at its thickest point).

The front of the device is coated in a tremendously shiny and extremely smudge friendly plastic. The 480 x 320, 3.1-inch capacitive touchscreen is totally flush with the surface of the device, and it just about runs edge-to-edge. Above the screen is a small silver earpiece, and below is the center button, which looks like a small metallic ball embedded in the plastic, but is actually partially transparent, making an LED inside visible when performing gestures (more on those in a bit). Around the left side of the phone are two small volume rocker buttons, on the right is the MicroUSB cover.

The top section of the phone has a hold / power button located on the upper right corner, and next to it sits the old Palm standard -- a ringer on / off switch. In the center is a 3.5mm headphone jack (yes!). The backside of the phone reveals the camera, tiny flash, and new stylized Palm logo.


Underneath all this plastic there's a TI OMAP3 processor (though we don't know what it's clocked at), 8GB of storage (of which about 7GB is user accessible), and an undisclosed amount of RAM (we're guessing around 256MB). There's also a proximity sensor and a light sensor, both of which work almost exactly as they do on the iPhone (like dimming the screen when you put the device to your ear to talk), and an accelerometer, you know... for making stuff flip around.

The Pre, of course, contains a sliding mechanism which reveals a QWERTY keyboard beneath. One of our first minor issues was the build quality here. There's nothing tremendously alarming about how these two pieces connect, but there is certainly a small give when the screen is in its closed position. Sliding the display up, however, definitely made us pause a bit. At first it doesn't seem like there's the kind of tight clicking action you'd expect here -- it does slide up and lock firmly into place, but there's a lot of play from point A to point B. For instance, if you slide the screen slowly, it's possible to just have it stick in a half open state, and we also noticed that there's a divot -- a stopping point -- early on when the slide begins which the screen seems to settle into a bit too easily. What we realized through repeated use, however, is that the faster you slide the screen, the sturdier the mechanism feels -- it's just not that obvious at first. Though we'd rate the general seating and feel a bit higher than the G1, we still wouldn't say that this is as good as it gets -- but it's certainly not a deal-breaker.


When you do slide out the bottom half of the phone, the shape takes on a more banana-like appearance. The bottom and top pieces curve along the same angle, making the phone just a bit taller than the iPhone and G1. Around back, a mirror is revealed when you have the keyboard out, though we'd like to stress that it's for men and women alike.

Besides the standard issues we had with the construction of the phone, we did spot another peculiar problem we hope is just a one-in-a-million fluke with the test device we were given: it physically broke.

There is a small flap that covers the MicroUSB port, and while attempting to get the thing open, a thin piece of plastic which runs along the bottom of the casing just snapped. Now, we're not saying this is a widespread problem -- in fact, reps at Palm claimed this was the first time they'd seen it happen -- but it was a little disconcerting. Still, hats off to them, because they went above and beyond the call of duty to bring us a second phone: they sent someone on a plane from San Francisco to LA!

Our personal damage aside, the Pre is a beautiful piece of technology, and it's clear that a lot of time and love went into the design. It's not perfect, and the quality of the components don't quite match up to those of the Storm or iPhone, but it's a really great looking, reasonably solid device that we'd be happy to show off to friends and loved ones.


Display

As we mentioned, the display is equal in resolution to the G1, Storm, and iPhone -- and just like those devices it's capacitive. In general we felt the clarity and vividness of color on the Pre was excellent. The screen gave us a little trouble in sunlight, however; due to the sheer glossiness of the phone, it was a bit hard to make out details on-screen unless we had it at the right angle. It's perfectly readable, just not best-in-class when it comes to direct daylight viewing.

Touch sensitivity was more than acceptable, though we do take issue with tracking and accuracy in some instances, particularly when you're close to the edges -- taps sometimes go unregistered and your aim can feel off. Our judgment is that it's not a screen issue, rather a software sensitivity quirk that could seemingly be fixed with an update. Overall though, the touch experience -- whether due to smart programming or the particular display used -- outclasses most other devices in this category (the iPhone still bests it in this department though).

Keyboard


Since this is a Palm phone, and since it's introducing the rarely-seen portrait slider configuration, the keyboard has been a subject of tremendous debate. Well, we can put your mind at ease folks -- it's actually pretty good. Now, we won't lie, it's not quite the barnstormer of the Bold or Treo 650, but it is a very, very solid typing experience nonetheless. The keys -- made of a similar rubbery material which the Treo Pro and Centros use -- have a surprising amount of depth given their location, and they're actually somewhat clicky (a surprise to us). Spacing between keys is ample, but we wouldn't say generous -- though in general getting accustomed to typing on the Pre wasn't too painful. Our biggest gripe is actually with the software, which omits some no-brainers like double-tap spacebar for periods (though in the phone's defense, it does have a dedicated period key). Auto-correction is in effect here, fixing your lowercase i's, un-apostrophe'd contractions, and the occasional misspelling, but it pales in comparison to the iPhone's intelligent input recognition. We're not quite as fast with the physical keyboard as we'd like to be, but we count our major gaffes or mistypes in the dozens on the Pre -- a number easily eclipsed when using one of its virtual siblings.

If you're worried about copy and paste, by the way, have no fear. Palm has certainly included it here, and simplified the process by employing the gesture area and keyboard for shortcuts. To move your cursor in a text field, you hold down the orange key and swipe in four directions to navigate. To select, you use the same technique, but hold down the shift key instead. Cutting, copying, and pasting are handled via combos of placing a thumb or finger on the gesture area and tapping X, C, or V.

Camera


Look, we're just going to say it: we love the Pre's camera. There are two things happening here that make it lovable. First, it's 3.2 megapixels, which makes it at least competitive with its contemporaries. Second, Palm has done something totally radical in webOS -- they've made it so the image processing is backloaded when you're shooting. What that means is that you can snap away without having to sit through the shutter lag you're probably used to, allowing you to actually use the thing like a real camera. Furthermore, the image quality we saw was more than sufficient for on-the-scene shots, with particular clarity and color in daylight shots, though a surprising amount of definition in low light situations as well. Oh, and did we mention it has a flash?

Of course, Palm doesn't provide a video option here, which should chafe some folks. Why they decided to leave it off is a mystery to us (we're going to guess a rush to push this thing out the door before their six months were up), but we'd be surprised if we don't see video recording come to the device in the future.


Audio quality

Audio on the Pre doesn't disappoint either. The earpiece is very clear and plenty loud, and according to the unlucky humans who've received calls from us, our outgoing sound quality wasn't too shabby (on one call using the speakerphone, the caller didn't even know we weren't holding the device). Speaking of the external output, we can say it's loud, though by no means perfect (we found its range to be a bit middy). It was certainly usable, due mainly to the fact that you can actually make out what your caller is saying, but we've been spoiled by the output of the Bold -- our new high-water mark for phone speakers. For playing music or anything beyond a simple conversation, you'll want to use that headphone jack (or stereo A2DP).

webOS / user interface


We're really reviewing two products here. One is the hardware, obviously. The other is the operating system which will be Palm's platform for mobile devices for the foreseeable future: webOS. Some of the ideas behind webOS -- a Linux-based platform which leverages web standards for development -- are revolutionary for smartphones. It dashes as many design paradigms as it adopts, so there's quite a bit that's fresh here. The real question is not if those ideas are revolutionary, however -- it's if they're usable.

Cards


The main focus of webOS is cards, essentially a list of open applications which can be moved into and out of with the press of the center button or a swipe of your finger. The emphasis here is on multitasking as well as reducing the number of steps required to go from one action to another. The premise is extremely simple, and in this implementation, extremely useful. Applications do seem to take a slight bit longer to load than those on competing platforms, but the beauty of the Pre is that you're not opening and closing apps that often. Additionally, if you're used to Windows Mobile or the BlackBerry OS, this is a major shift -- instead of obscuring what apps are open, you can almost instantly snap to a clear picture of what you're working on. The idea allows for some pretty interesting use cases, like being able to jump back and forth between a webpage and an SMS thread, or out of a call, into your weather application, and back into the call with little effort. You can rearrange the card order, and when you're finished with an app (or when you tax your memory), you can just swipe up on one of the cards to quit, though it keeps your data in a save state so you're not back to square one when you reopen.

Our take? The concept and execution on cards is excellent. The experience of using them to get around during the day feels like half application switcher and half active widgets, and is completely appropriate for a mobile device. Additionally, Palm warned that after seven or eight apps, depending on footprint, we'd have to start closing some items to save memory, but we've taken the Pre up to 12 apps and beyond (including four browser windows, email, SMS / AIM conversations, the AccuWeather app, Pandora streaming in the background, dialer, and more) with no issue. The overall OS does seem to get a little sluggish as you pile on the programs, but certainly never to a point that was unusable. We did experience some freezes and a handful of crashes, but only when we pushed the device extremely hard.

Gestures


Cards aren't the only angle Palm wants to push, of course. The Pre is navigated through a series of gestures, most geared towards one-handed operation. The touchscreen actually runs into the black plastic beneath the screen, into what Palm calls the "gesture area" (go figure), and that's where a lot of the action happens. The center button -- and two LEDs on either side of it -- glow softly when you swipe in this section, creating a kind of trail or landing strip for your movements. The basic set of gestures you need to learn (and you do need to learn them) are as follows:

  • Swipe up: zooms you out from an application, brings up the launcher, closes the launcher
  • Slow swipe up: brings up the Quick Launcher (or "wave," as we like to call it
  • Swipe left: goes back in pages in the browser, back through sections of an application, eventually takes you to card view


The phone also has more familiar movements, like pinch, double tap, and a standard flick left and right. As we mentioned, there is a learning curve, especially coming off of an iPhone, but it's not too steep. Mostly, these gestures are intuitive and helpful, but we do question a few decisions Palm made here. For instance, when you want to bring up the launcher and you're in an app, you have to swipe up to zoom out to the card view, and then swipe up again to get the launcher up. Why the extra step? We have no idea.

Notifications



Here's another major score for webOS. Instead of obtrusive pop-ups, Palm has opted for small wedges that appear at the bottom of your display with a message and icon (sometimes accompanied by a little chime, as in the case of a new email). As these gather, your content above scales to fit in the space allotted -- it sounds like it could get messy, but it's actually an elegant solution. Not only do the messages collapse into a single, manageable line until you're ready to deal with them, but you can swipe away alerts once you've read them.


There are also certain apps which plug into that space when in use, allowing you to control them even if they're in the background. An excellent example would be Pandora and the included media player. Both applications give you a small menu which expands and collapses on touch, revealing controls for the players, and in the case of Pandora, the thumbs-up or thumbs-down symbols used to rate the music you're listening to. It's an ingenious idea -- one which we're sure developers will find all sorts of creative ways to use.

Finally, a third type of notification is meant to force your attention toward it, such as a calendar event. In those cases, you're given the option to dismiss or snooze the alert.

Launcher / Quick Launcher


The launcher and quick launcher should seem pretty familiar to most smartphone users. The standard launch window is almost identical to the Android or iPhone gridded home screens, but in addition to being able to swipe left and right through individual pages, you can scroll up and down on each page as well (so you have room for more than just nine icons). To rearrange icons you tap-and-hold, and webOS auto-shuffles placement as you find a spot for your selection. You can move and remove icons from the Quick Launcher in the same fashion, but you're limited to four interchangeable choices, and stuck with a largely useless arrow icon that's only used for pulling up the launcher window. We don't get that part, since you're given a gesture to do the exact same thing.

The Quick Launcher sits at the bottom of the screen when you're in the launcher window or card view, but disappears in apps. To bring it up, you can slide your finger slowly up the length of the screen. It's a neat trick, but we didn't find it much more efficient then using the standard launcher, though for things like the browser and camera it did make some sense.

Universal Search


The first thing you should know about the Pre's Universal Search is that it isn't really all that universal. From the card view or launcher, the find-as-you-type engine allows you to look up contacts, applications, and if all else fails, take your query to the web via Google, Google Maps, Wikipedia, and Twitter Search. What it doesn't do, however, is let you search any actual content on your device, like a mail message, an SMS, or a document. In that sense, the term "universal" is somewhat misleading, though we'll give Palm props for making it work as quickly and painlessly as it does. We're going to call it out right now: Palm needs to extend this feature to mail at the very least -- we're happy that we can jump quickly to a contact or internet search (really really happy), but we've honestly gotten pretty used to iPhone OS 3.0's broad searches.

Look and feel / other thoughts


Simply put, webOS is absolutely gorgeous. As far as phones go, it's not just the only device we've seen which competes with the iPhone for looks, but we'd go as far to say that it bests the iPhone in some categories. The selection of fonts and font styling, use of transparencies, unified look of all of the elements, smooth transitions, and detailed application icons tie together in a really elegant way. It's clear that Palm's designers took a page from the Apple playbook here, but when something looks this good, you can hardly fault them. As our man Oscar Wilde said, "Talent borrows, genius steals."

Generally speaking, the Pre's UI makes sense and makes it easy to get things done rather quickly and painlessly. It is an impressive beast, though a beast nonetheless -- and that means taming will be in order. We saw plenty of little glitches: messages that wouldn't pop up (or go away), transitions that hung for a bit, and we definitely had a crash or two. In particular, it seems like Palm still needs to work on memory management -- we noticed the device getting a little laggy after a day of heavier use, so we're thinking not every process is being killed completely.

Keeping us hopeful about these issues is the way in which Palm plans to address them. According to the company, updates for the phone will be made OTA as necessary, which means they'll be able to put out fires quickly, and respond to customer needs with greater agility than a lot of their competition. We have a feeling we'll see a handful of fixes just after launch based on our conversations.

There's certainly room for improvement, but in 1.0, webOS has leapfrogged a lot of the competition, and seems to have its sights set higher than that.

There's a lot new in the Pre. It's not just the phone and it's not just the OS -- it's the underlying ideas and bundled applications too. We're going to try and run down the stand-outs and standards -- from the heady promises of Synergy, to the basic stuff you'll be using every day.

Synergy


Besides things like Universal Search and unobtrusive notifications, another really big idea that Palm has for webOS is Synergy, a contact / calendar management system that aims to put an end to the confusion of having to juggle multiple accounts from multiple services on a single mobile device. Unfortunately, this is probably the aspect of the OS that needs the most work.


The Synergy premise is simple: it will take your Gmail account, Facebook profile, AIM identity, and / or Exchange data and merge it all together on your Pre, killing duplicate entries, joining together sources where there's overlap (creating "linked contacts"), and generally making your connected life super-duper awesome. What it actually does is dump pretty much all of your content into the phone without a second thought for what it's letting through the door. If you have a single Gmail account, you'll probably be okay -- it perfectly handles a set of data from one source just fine, and that source would be easily manageable because... well, it's your Gmail. However, it's totally indiscriminate about what contacts it pulls in, which means if Google has auto-saved anything, it's going to be on your phone. That's fine, we're used to this. The G1 does the same thing. The problem really arises when you want your Facebook profile integrated. Guess what? You don't get to say whose info gets pushed to the phone -- every single person you "know" on Facebook will instantly becomes a part of your contact list. And we're talking people who only give you access to their birthdate. How does it feel to have a contact on your phone that is simply a birthday? Annoying.

We don't know if you're like us, but we don't want every person we're friends with on Facebook in the contact list for our phone. Facebook kindly provides grouping for different contacts because it appreciates the fact that not everyone has the same kind of relationship. WebOS? Not so much.

The system works fine if you don't care who ends up in your address book -- in fact, it works really well at grabbing all that info and sticking it on the phone (while keeping it in sync with server-side changes). Where it breaks down is giving you any kind of tool to really manage and gatekeep the information.

Secondly, contact linking doesn't seem to work the way it should -- namely, it doesn't find duplicates in all contacts, whether an AIM, Google, or Facebook account and merge where appropriate. What we discovered is that that adding our AIM account to the Gmail contact list that lived on the phone didn't automatically bring the correct names under one roof (as you imagine it's supposed to). Instead, we had to manually link contacts, even when we could clearly see that the AIM name was already in our Google contact. That's the opposite of what Synergy is supposed to do... we think. We spoke to Palm and confirmed that for now, Synergy isn't pulling in AIM names, only email addresses, though they're considering one of those OTA updates to fix once the device is launched.

Don't get us wrong -- there are a number of good ideas at play with Synergy, but it clearly needs some kinks worked out before it realizes the vision that the company seems to have for it. For the time being, we'll likely only be juggling our AIM and Gmail account data, though we're ready and willing to see what happens with that aforementioned OS update.

Contacts and Calendar


Since contact management with Synergy can be handled in multiple locations, we expected fairly robust options when it came to our address book -- and we weren't disappointed. The contact app in webOS is extremely well thought out and easy to navigate. As you'd imagine, if you're using Gmail as your main contact list (as we were), changes to contacts are updated periodically. We were hoping there would be a push and pull, but no luck. Still, you can choose to manually sync when you want to update, and changes seemed to flawlessly take whether we made them in Gmail or on the phone. One option we'd like to see in the future is for Synergy associations to be allowed to migrate back to your Gmail / Facebook contacts. For instance, if you link an AIM account and Gmail contact on the Pre, when you sync back to Gmail, it will add the AIM name to that entry. Still, we think webOS provides a deep and useful platform for managing contacts, despite some of the shortcomings of Synergy.


The calendar app, like contacts and email, will automatically sync to your Gmail (or Facebook / Exchange) set and pull data in. Besides offering helpful views in a variety of colors (though not enough variety for our needs -- this app is hurting for user-selectable hues), it also can hook into / be hooked into other applications on the device. For instance, you can buy tickets for a movie via Fandango, and have it drop the event in your calendar. Like contacts, calendar merging is an all or nothing affair, though you can choose which calendars you see in your views.

Navigation in the app is actually really clever -- this is the first calendar application for a smartphone that didn't feel like it was trying to cram too much information into too small of a space. Admittedly, the week and month views aren't going to reveal lots of detail to you -- you'll have to go day-by-day to see that info -- but for giving a clear overview of your events (provided you know which colors are which), it does an outstanding job. We also liked the fact that it used the familiar left / right and up / down swipes to move through days, weeks, and months, which felt completely native and natural to the webOS environment. It's obvious that as with previous applications, Palm needs to work out the Synergy kinks, but this is clearly a place the company didn't skimp on.

SMS / Instant messaging


Unlike some of the misses in the Synergy arsenal, the way it brings together SMS messages and IM'ing is actually one of the coolest and most interesting parts of the phone. Essentially, Palm has taken the threaded messaging it pioneered in its Treos to the next level, allowing conversations that take place via SMS to be fluidly carried into an AIM or Google Chat session, and back out again. The messaging app on the Pre allows you to simply toggle which service you're using, and keeps all the messages in a clear, easy to read timeline. On your end, it looks like the same continuous chat, though you're jumping from space to space. In both theory and practice we love this idea -- it simplifies quick communication, and keeps a thread going where it might otherwise be lost. Visually and from a UI standpoint, the messaging app is clear and simple, leaving room for it to do what it does best. The only danger you have here is confusing the person you're talking to, since they're receiving those messages in multiple places.

Email


For us, the email application included with webOS is a double-edged sword. In terms of general usage and simplicity, it's excellent, and the inclusion of push Gmail is massively exciting. Unfortunately when it comes to deeper functionality, customizing, or more robust sorting and management options, however, we found ourselves wanting more. A lot more.

The basic design of the app is very similar to Mail on the iPhone, save for one big missing puzzle piece: there's no multiple message management. What that means is that you've got to individually delete or file every single message you get -- that was okay in iPhone OS 1.0, but it feels downright outdated here (and Android 1.5's check boxes are real salt in this wound). We're just reminded of what a huge pain it is. For a device that's meant to be focused on getting things done, this is a remarkable oversight. Additionally, we had hoped that since there was such tight integration with Gmail in webOS that we'd see some Google-centric features, such as threaded messages or labeling / archive abilities that played a little nicer with the big G's system. Unfortunately, none of that is present here. You do get to layer accounts, as in other aspects of the OS, though it seems a lot more obvious in mail, since managing multiple accounts in a single pane is really nothing new.

Other minor nitpicks concern the lack of options for changing font size, no choice on message preview length, and the fact that all of our emails from the Pre seem to be colored navy blue, and there's no way to change it. C'mon guys.

To be clear, mail on the Pre is definitely usable -- especially given push, which usually serves up messages within seconds of hitting the server -- but we would have liked to (and hope we will) see more. There's lots of room for improvement in this space, webOS or otherwise.

Phone



The phone app is extremely basic, but we assume that's because hooks for calling out are strewn all over webOS. Essentially you're offered an iPhone-like dialer, which gives you fast access to your voicemail (sorry, no visual voicemail here), contacts, and lists of your recent / missed calls. During a call, you have options for speakerphone, mute, back to the dialer, and adding callers. There's nothing drastically wrong with the phone app on the Pre, but there are some gaps in logic that we don't follow. For instance, when you dial digits, it doesn't search your address book for strings and pull up matches from your contacts list... it just lets you dial. And though we had originally observed that you couldn't use the QWERTY to type-to-find your contacts when using the dialer, it turned out there is an option to switch on this functionality. Why it's not automatically switched on to begin with is anyone's guess.


Other than a few confusing elements, making and receiving calls on the phone is about as straightforward as one would expect. We were incredibly pleased to see that Palm has included speed dial for your contacts, making use of the entire QWERTY (save for E -- that's for voicemail) for long press insta-dial. If the contact hunt in the iPhone has you down, this is the antithesis: a beeline to your most used numbers.

Browser



The webOS browser is obviously central to the operation of the OS as a whole. Since many apps on the device leverage web standards for their core operation, it could be said that the browser is the OS. But in terms of a straight-up web browsing, we found the Pre's out of the box option fantastic -- not only in speed and navigation, but with rendering and compatibility. Built atop WebKit (just as Apple's Mobile Safari), the webOS browser displays pages almost exactly as the iPhone does, though due to the fact that Palm is implementing a lot of hiding icons and app controls, it actually feels like you're seeing more content despite the smaller display. Additionally, its cache management seems better to us, allowing for fairly speedy back and forth through multiple pages. We did see a few rendering issues on pages here and there (like being able to scroll beyond where any content lived), though in defense of the browser, most of them cropped up in places like lyrics sites and old Angelfire pages (we kid, we kid).


Zooming is accomplished via double taps as well as pinching, but unlike the G1, the rendering and snap points on the Pre are formatted to follow columns, just as Apple's iteration is. That means that when you double tap on a chunk of text or an image, nine times out of ten you get exactly the right sizing for that content.

When it comes to multiple pages, instead of creating tabs, the browser just opens another instance in your cards. This can be a little confusing at first, but once you get used to the idea, it's actually a really great tool for managing a handful of data at once. Meanwhile, history and bookmarks are always accessible from a drop-down menu, but Palm also provides a kind of speed-dial screen when you first open a blank browser page, giving you quick access to your top bookmarks.

As far as mobile browsing options go, the Pre is about as good as it gets -- nearly on par with the iPhone in rendering, though more cleanly laid out, easier to navigate, and (in our tests) downright faster.

Media playback and management



Palm definitely scores with its concepts about handling media in webOS, particularly when it comes to music. First, they've given users more than a single option to load media onto the device, allowing for a straight iTunes sync (more on that in a moment), but also giving you the option of loading media onto the Pre in mass storage mode. The phone automatically recognizes file types and throws them into the appropriate application regardless of location in memory (which means you can organize however you like).

iTunes sync (or "Media sync" as they call it), however, really helped ease us into using the Pre as a media device. In essence, the process works exactly as it would if you were using a standard iPod. You get options for (un-DRM'd) music, TV, movie, podcast, and photo syncing just as you would on an Apple device, and in our experience, the actual process was no different. iTunes offers up a contact sync, though it doesn't actually appear to do anything but store a backup file on your phone -- not a huge deal, but it would be amazing if it worked. Regardless, the ability to easily manage your media library will take a big load off of the minds of potential switchers worried about how to deal with a new platform... but we can't imagine Apple is super stoked by the concept.


As far as playback goes on the phone itself, we couldn't be more pleased. The Pre forgoes glitz like Cover Flow, instead relying on clearly delineated lists and a really smart (and attractive) shuffle function that make it easy to get around your collection. One of our favorite features is the ability to jump to an artist or song search via YouTube, or an artist search in Amazon's MP3 store while browsing or playing back music. It's a really smart little perk that makes it way easier to go deeper on something you're enjoying -- and it's the kind of 'why didn't anyone else think of that?' concept that makes webOS so enjoyable to use.

Video

Video management is pretty straightforward, but we found that's not quite so simple to get that content playing right on the Pre. Mostly the device seems a bit finicky about what formats / conversion types it will take. Anything converted for an iPhone should work perfectly, but if you're throwing on other MP4 / M4V content, you might run into some snags. Obviously, anything protected won't play, and even movies that we'd converted for upload to YouTube (MP4, not Flash, obviously) didn't seem to want to work. Still, H.264 videos we grabbed from the internet, such as a Tekzilla video, played just fine. Running video and music content definitely puts a little strain on the system, and when you've got something loaded up and playing, you'll notice a speed hit in opening / closing of cards and applications.

Amazon


The included Amazon MP3 store integrates with the Pre beautifully, save for one glaring omission: you can't download files over EV-DO. Just like the first iteration of the iTunes Store on the iPhone, you've got to have a WiFi connection if you want to bring down tracks. We don't know if this is a network issue for Sprint, or just a weird quirk the two companies didn't see as a problem, but we're not happy unless we can actually use the Rev. A we've got here. Palm and Sprint: fix it.

Applications


Memos, Tasks, Clock, YouTube, Maps



Just like most modern smartphones, Palm throws in the old standards here. YouTube and Google Maps operate largely as they do on other platforms, though admittedly, we prefer the look and feel on the Pre. In particular, Maps seems much easier to get around in with its pop-over menu for deeper options. Directions seemed better implemented to us too; webOS gives you dedicated controls which don't alter your view for moving forward and back through each step. If you have to look at the list, jumping into and out of it is a one-tap process.

Palm also offers up the kind of utility apps you'd expect. A snazzy looking retro clock, the eye-candy Memos app (sticky notes on a corkboard... cute), a decent calculator which also sports a kind of 70's vibe, and most notably, a Tasks app. The latter is notable for two reasons -- the first being that we're totally in love with the design, which takes more than just inspiration from Moleskine notebooks. Secondly, it's a really useful app that lets you keep sets of to-dos and create due dates and alarms -- though what we'd like to see some integration with Google's recently minted Tasks for Gmail.

One other note (no pun intended): we made a promising discovery with Memos -- you can actually search the content of your notes within the application, find-as-you-type and all. We're hoping it's a sign that Palm means to implement searches for other content in webOS... like email, perhaps?

Sprint Navigation



We won't go into detail on every Sprint app included (especially not the NASCAR app), but we wanted to briefly talk about Sprint Navigation. Since most other smartphones of this class either don't come with on-board GPS navigation, or charge you for it, we felt it was notable that Sprint and Palm are giving away what feels like a very usable GPS app with the Pre. We used the software -- which does turn-by-turn / text-to-speech directions -- while driving from San Diego to LA, and it worked flawlessly. Our only complaint is that you can't put the phone into landscape view while using it (hey, what is that accelerometer for?), and there doesn't seem to be a car mount available, so finding a place to keep it wasn't exactly a cinch. Still, when you consider that this comes as part of any Pre plan you pick on Sprint, it's a really, really nice addition.

PDF View / Doc View



We're not heavy document users, but we do need to load the occasional PDF or spreadsheet. The Pre seemed to have no trouble opening simple PDF files and Word documents in the two provided applications, though we started to see some nasty memory management issues when we busted out large files, like a 7MB PowerPoint document. PDF View also seemed to buckle under a 3.9MB file, essentially freezing the phone, then giving us a memory warning that we needed to close cards (we only had two others open). Clearly this stuff hasn't been optimized, but we're hoping that when DocsToGo makes its way onto the Pre (apparently it's forthcoming), it will be able to tackle larger files without so much heartache.

App Catalog



We really liked the interface for browsing and downloading apps on the Pre. Instead of landing on a homescreen which only gives you a small amount of info, right off the bat the App Catalog presents you with a cleanly laid out list of featured apps, popular, and then a nice selection of tag-based sorting methods if you want to go deeper (most recent, category, etc.). Once you get into a tag, you're given a menu for parsing by date added, app name, rating, or cost.

Getting more info (including screenshots) and downloading was a pretty pleasant experience, and the layout is spacious but still info-packed; you feel like you're not missing anything. Screenshot browsing was nice (something we regularly desire in Android's implementation), and actual application pages had easy links out to developer websites and support. In case you're wondering, everything was free on our review unit, so we didn't get to try out any pay-to-play apps (thanks guys!).

We do have a gripe, of course. App Catalog doesn't seem to support background downloads within the application itself (you can use other apps while it works), so if you begin a download and want to go back a page and browse the list, your file stops transferring. It's a little ironic that the phone which boasts multitasking as one of its big features couldn't give us a queue for ongoing downloads.

Third party applications


At the time of this writing, there were but a handful of third-party applications available in Palm's App Catalog for download. Some of the standouts to us include AccuWeather, Pandora (obviously), Tweed, Fandango... and Classic (the Palm OS emulator, in case you've been on a desert island, under a rock, etc.). We're not going to work through all of the applications which will be ready at launch because it would probably make this a four-part review (and no one wants that). Still, we do have a few random thoughts.

Classic is most interesting because it shows the possibilities of what the Pre can do -- though it's obviously one of the few here that isn't built using just the web-standard tools which Palm is pushing on developers. To be honest, we had hoped to fire up the app and run Dream Engine, a Turbografx-16 emulator that was a favorite of ours back in the Treo days. Unfortunately, it doesn't look like the app has access to any file systems -- we couldn't get the program to recognize our ROMs folder, no matter what configuration we tried. Attempting to peek at the directory structure with FileZ also proved futile. We're hoping that Palm will open this up a bit more... but we're also hoping they'll open the platform a bit more too.

Speaking of, developer courting still seems like an area where Palm needs work. They've got a great OS to work with, but they have yet to really extend a hand to a wide selection of developers or help explain how working in webOS will be beneficial to their business. The platform is nothing without the support of creative and active partners -- just ask Apple. Here's a chance for Palm to further set itself apart from the competition. We're hoping they take it.
Data performance


A smartphone of this caliber is nothing without a decent network to cruise on, and we were really pleased with data over Sprint's EV-DO option. Since we weren't testing side-by-side with another Sprint device, we can't tell you how it stacks up to something like the Instinct, but running side against the G1 and the iPhone on their respective networks, we definitely saw favorable results. In a somewhat unscientific run of repeated DSLReports mobile speed tests, we found that the Pre averaged 634Kbps downstream, while the iPhone and G1 nabbed 552Kbps and 413Kbps, respectively. Not drastic differences -- and obviously only in a single location -- but certainly promising if you've got good Sprint coverage.

In terms of daily use -- or what the phone actually felt like -- we found that data pushes and pulls were non-obtrusive, and it didn't seem as if we were anxiously waiting for even robust pages like Engadget to load up. Our major gripe is actually directed at Sprint's network: you can't do voice and data concurrently with EV-DO, which meant that we were constantly getting a spew of emails after speaking to someone on the phone. The problem is circumvented if you're in WiFi range, but that doesn't help you if you're on the road. The same goes for web browsing or any other instance where you need to use data -- you're not going to be checking out sports scores while talking to your buddies, and that kind of stinks.

Backup / restore


Palm offers a new service called Palm Profiles, which promises to never leave you in the lurch should you break or lose your device. Like syncing via iTunes, it's meant to store your important user data, such as preferences, email account settings, and what applications you've downloaded. Unlike iTunes sync, however, Palm Profiles are backed up periodically in the background, over-the-air -- meaning you don't actually have to do anything to keep your info in place. Since we had a second device delivered to us by Palm, we got a really good preview of what it would be like to use the service.

In not so many words, it works... kind of. When we swapped devices and input our Palm Profile login into the new phone, it warned that another device was registered, and that it would be pulling that data down to our new phone (along with a warning to backup any files we added via mass storage mode). Then it did some kind of secret Palm voodoo where it filled our device with apps, settings and data from the other phone. It wasn't without issue, however, as we found that details like brightness settings and ringtone selections hadn't carried over to the new phone, and more shockingly, we found that when it restored our AIM and Gmail accounts, it unlinked all of the contacts layers that we'd hand-linked. Not so cool.

It did do most of what it promised, but we'd like to see some extensions to this service. It should at least get your preferences right if nothing else -- though we won't complain too much about a feature that saves us the trouble of having to re-add all of our data.

Battery life


We didn't have the time or the resources (like multiple users) to put the Pre through the kind of lengthy, hard-hitting, take-no-prisoners battery testing some of you might want, but we did have a chance to use this as we would our own device for a pretty good run of days (we'll likely do a follow-up post with harder numbers for specific tasks, like media playback).

In terms of real-world use, the Pre battery situation is good, not great -- though we think that you can (mostly) put your Apple-inspired fear of background processes to bed.

During heavy use -- phone on all the time, browser testing, media playing, lots of conversations -- we could make it about three quarters of the way through a day without having to plug in. We weren't over the moon with how quickly we noticed the numbers dipping, but we also weren't completely surprised. Compared with the G1 (and we're talking 1.5 here), we'd say the Pre does a tiny bit better (or very close) on battery life -- but if you're a heavy talker or plan on running media on this all day long, you'll be reaching for the charger (or second battery) come dinnertime.

Still, for the battery size (1150 mAh) and amount of data being pushed, it didn't seem like the phone was performing unreasonably, and we don't knock the fact that you can snag a second (or third!) battery if you know you're going to push it. During the more conservative days -- which we think reflect the kind of moderate use we put our phones through -- battery life declined much less noticeably from morning till night. We'll be keeping our eyes peeled for third-party options with more juice, but the brick in the box isn't too shabby at all, especially given our expectations.

Bluetooth


We didn't have a wide variety of devices to test the Pre with when it came to Bluetooth (we were on the road for the entire review period), but we did have an Aliph Jawbone and Motorola ROKR S9-HD on hand. Our experiences with the two devices were slightly different.

For the Jawbone, no matter what we tried, we couldn't get it to pair with the phone. We would have been more alarmed with this situation, but we're not entirely convinced it's the Pre's fault. We couldn't get the thing to pair with our iPhone either. We're leaving the verdict out on this one, because our experience was far different when testing out the S9-HD.

Obviously, stereo A2DP is a feature that end-users are becoming more and more accustomed to seeing on their devices -- we think Apple's addition of the option in iPhone OS 3.0 speaks to that. Palm smartly saw fit to include it out of the box with the Pre, and it seems to work perfectly. Pairing with the headset only took a few seconds (once we'd charged the thing up, of course), and the Pre flawlessly switched over from playing audio out of the external speaker to the Moto device. Quality was excellent, though in this case, you've either got a connection or you don't. Overall, the experience was about as painless as it gets -- and we see ourselves putting the feature to quite a bit of use.

Accessories


The Pre ships with a MicroUSB cable, a small pouch, and a wall adapter for charging. There's also a pair of earbuds in the box with an attached remote and microphone. In terms of fit, this may really be the area where Palm is trying to outdo Apple... in badness. We mean the buds don't fit in your ear well, if you're not catching our drift. That's kind of sad, because they're not bad looking, and they actually sound really great -- if you can manage to keep them in your ears. But you probably can't. It's a real missed opportunity for Palm, but at least you've got a standard jack that you won't have trouble filling. Seriously, can anyone get this right?

Otherwise, there's a car jack kit, which we've already seen for the Treo Pro and... a little something known as the Touchstone.

The Touchstone has been the subject of a lot of attention given that it's the first induction charger for cellphones that a major manufacturer has offered, and it clearly has a lot of "wow" potential for people who aren't familiar with the technology.


Don't get us wrong, we think it's really quite cool, but in terms of practical use, we're not sure it's a must-have accessory for the Pre -- especially at $70. Yes, it's definitely great to be able to throw the phone on there for charging without mucking about with cables, and we actually prefer the soft-touch back to the glossy one which ships with the phone, but there were a few minor issues we had with the Touchstone that could make it less desirable to some. For starters, when you're charging on the Touchstone, the phone display dims but keeps the time on the lock screen... and there doesn't seem to be any way to switch it off. That may be fine if you don't mind the glow, but we didn't care for it and we don't like the idea of not having control over this setting. Additionally, the phone seems to charge much more slowly than with a direct-to-adapter connection, and the backside of the device can get pretty hot while it's on the base.

It's certainly a conversation starter and a showpiece, and we could see it for use as a secondary charging option, say, if you're using the phone for some A2DP in your living room and want an easy way to keep it juiced. Ultimately though, we think it'll be a bit of a challenge to pry that money out of most buyer's hands for something so superfluous.

Pricing


Given its undeniable status as a hero device (the hero device?) in Sprint's lineup, and considering the high-end phones it's designed to fight, "value" might not be the first thing that comes to mind when talking about the Pre, but it's not just about saving $10 or $20 month to month -- over the course of a couple years on a carrier contract, even a modest difference amongst plans can turn into hundreds or thousands of dollars. On paper, Sprint seems to have the clear-cut advantage here over the other nationals -- Verizon, AT&T, and T-Mobile -- on account of its hyped $99 Simply Everything plan that it's pushing harder than ever with the launch of this device. But in practice, what does it mean for your wallet?

For phones like the Pre and its contemporaries, it's a forgone conclusion that you want unlimited data -- email with attachments, powerful mobile browsers, and streaming video all collaborate to make it a non-negotiable requirement these days. As for messaging, granted, not everyone's blowing through thousands of text and picture messages a month, but the capability is more important (and better implemented) than it ever has been before, so you may as well lump it in. Really, that leaves only voice calls as the wild card -- some smartphone users make a handful of calls a month (often these are the same folks working their thumbs raw on texts), while others are on the horn several hours a day. To that end, we wanted to break down what the Pre's going to cost you over the course of a two-year haul versus its closest competitors -- Verizon's BlackBerry Storm, AT&T's iPhone 3G, and T-Mobile's G1 -- on unlimited and relatively low-minute voice plans.

As its name implies, Sprint's Simply Everything plan is... well, simply everything. $99.99 gets you unlimited voice, on-device data (sorry, no free tethering here), and messaging of all types. As we mentioned before, you get Sprint's TeleNav-powered navigation at no additional charge, which most other carriers bill for as an a la carte service. On Verizon, you're paying $99.99 too -- problem is, that's only for voice. The closest thing to unlimited messaging on Big Red's going to be the 5,000 plan, which runs another $20, data for $29.99, and VZ Navigator for $9.99. All told, you're paying $159.97. Similarly, AT&T will cost you $149.99 (of course, turn-by-turn's not an option here) and T-Mobile -- commonly considered the value leader -- takes second place at $124.98. At the end of 24 months, that means you would've shelled out $2,599.75, $4,039.27, $3,799.75, $3,179.51, respectively, after you take the costs of the phones into account; Sprint wins by a country mile, and there's a stunning $1,439.52 savings against its most expensive competitor, Verizon. Sticker prices on phones are subject to near-constant variation thanks to regional fluctuations, rebates, and moon phases, but even if the Storm were free and the Pre were $500, you'd still come out well ahead.

Stepping down to more modest voice allowances, Sprint loses -- but only because T-Mobile cheats. On Sprint, you'll pay $69.99 for 450 minutes, totaling $1,879.75 over the duration of your contract including the cost of the phone. Verizon gets you going for $99.97, or $2,599.27 over 24 months and AT&T goes for $89.99, $2,359.75 in total. T-Mobile doesn't offer a 450 minute individual plan, but you can step down to 300 with no myFaves for $29.99, which means $64.98 with features added or $1,739.51 by the time your two years of indentured servitude is up. So yes, T-Mobile comes out on top here, but only because you're getting short-changed a smidge on the voice bucket.

In the final analysis, this is definitely a valid talking point for Sprint and something would-be Pre owners ought to consider. Granted, no one's going to question that Verizon's got a larger coverage footprint -- but if Sprint works everywhere you need it to, you're basically looking at a new laptop, a bunch of steak dinners, or a metric ton of ramen by the time you've worked your way through a full contract.

Wrap-up



It's not easy to sum up things as complex as webOS (a totally new operating system and UI) and the Pre (a totally new piece of hardware) in a tidy closer. Even if we could strip away all of the superfluous details and just look at those two aspects of Palm's work in a vacuum -- not accounting for things like carriers or price-points -- it still wouldn't make the job of leveling a verdict much simpler. Still, it's gotta be done, and we wouldn't want anyone else at the reins. So... what do we make of the Palm Pre?

There's no question that Palm has built this phone on the foundations laid by numerous devices before it -- most obviously the iPhone -- but the Pre clearly carves out its own path as well. Some of the ideas and concepts at play in webOS are truly revolutionary for the mobile space, breaking down lots of the walls that separate the experience of using a dedicated PC versus using a handheld device. One feeling that we were constantly stuck by while testing the phone was a kind of revelatory, 'Hey, this actually feels how a computer feels.' It was an experience not completely unlike our first encounter with the iPhone -- that little light that goes on that tells you that things can really be different than how they've been before. We also felt that same thing the first time we picked up a Treo, so it's fitting that the Pre should inspire a similar response.

To put it simply, the Pre is a great phone, and we don't feel any hesitation saying that. Is it a perfect phone? Hell no. Does its OS need work? Definitely. But are any of the detracting factors here big enough to not recommend it? Absolutely not. There's no doubt that there's room for improvement in webOS and its devices, but there's also an astounding amount of things that Palm nails out of the gate.

Still, if you're considering the Pre right now, you have to debate whether or not you want to hop onto Sprint's network. If you're already a customer and you're looking for a new phone, this one is a no-brainer -- but is this enough to lure you away from another carrier? We've debated (and continue to debate) the point ourselves -- though it looks like given what AT&T and Verizon are saying, that might not matter pretty soon. We will say that our experience on Sprint's network has been excellent, and its pricing more than competitive, though being mostly limited to North America is certainly a major factor when making this decision. There's also no guarantee of developer support with this phone. As we mention earlier, Palm needs to stoke those fires or the Pre will quickly be cemented as a tiny island in a large sea. We think the platform looks very promising, but with no big push (yet) to put a great SDK into dev's hands, and no existing userbase for those apps, it's hard to feel assurance that the software will come.

Ultimately -- carriers and developers notwithstanding -- what Palm has done is a major feat for a company of its size (and its dire position), and we think it's an important step in the evolution of mobile computing. Just like the iPhone's notches up the ladder, and the G1's contributions, the Pre moves the game forward in a very real way. We know this won't be the last of the webOS devices, and we know that as Palm improves its products, so will Apple, RIM, Microsoft, Google, and the rest of the smartphone gang. Unfortunately for them, their work just got a little bit tougher.

engadget.com
Share:

Nokia N900 Review

Today, Nokia stands at a fascinating fork in the road. Let's consider the facts: first, and most unavoidably, the company is the largest manufacturer of cellphones in the world by a truly sobering margin. At every end of the spectrum, in every market segment, Nokia is successfully pushing phones -- from the highest of the high-end (see Vertu) to the lowest of the low (the ubiquitous 1100 series, which as far as we can tell, remains the best selling phone in history). The kind of stark dominance Nokia has built over its competition certainly isn't toppled overnight, but what might be the company's biggest asset has turned out to be its biggest problem, too: S60. In the past eight years, Nokia's bread-and-butter smartphone platform has gone from a pioneer, to a staple, to an industry senior citizen while upstarts like Google and Apple (along with a born-again Palm) have come from practically zero to hijack much of the vast mindshare Espoo once enjoyed.

Of course, mindshare doesn't pay the bills, but in a business dominated by fickle consumerism perhaps more than any other, mindshare foreshadows market share -- it's a leading indicator. Put simply, there are too many bright minds with brilliant ideas trying to get a piece of the wireless pie for even a goliath like Nokia to rest on its laurels for years on end. Yet, until just very recently, it seemed content to do just that, slipping out incremental tweaks to S60 on refined hardware while half-heartedly throwing a bone to the "the future is touch!" crowd by introducing S60 5th Edition alongside forgettable devices like the 5800 XpressMusic and N97. A victim of its own success, the company that had helped define the modern smartphone seemed either unwilling or unable to redefine it.

Not all is lost, though. As S60 has continued to pay the bills and produce modern, lustworthy devices like the E71 and E72, the open, Linux-based Maemo project has quietly been incubating in the company's labs for over four years. What began as a geeky science experiment (a "hobby" in Steve Jobs parlance) on the Nokia 770 tablet back in 2005 matured through several iterations -- even producing the first broadly-available WiMAX MID -- until it finally made the inevitable leap into smartphone territory late last year with the announcement of the N900. On the surface, a migration to Maemo seems to make sense for Nokia's long-term smartphone strategy; after all, it's years younger than S60 and its ancestry, it's visually attractive in all the ways S60 is not, and it was built with an open philosophy from the ground up, fostering a geeky, close-knit community of hackers and devs from day one. Thing is, Nokia's been absolutely emphatic with us -- Maemo's intended for handheld computers (read: MIDs) with voice capability, while S60 continues to be the choice for purebred smartphones.

So, back to that fork in the road we'd mentioned. In one direction lies that current strategy Nokia is trumpeting -- continue to refine S60 through future Symbian revisions (with the help of the Symbian Foundation) and keep pumping out pure-profit smartphones in the low to midrange while sprinkling the upper end of the market with a Maemo device here and there. In the long term, though, running two platforms threatens to dilute Nokia's resources, cloud its focus, and confuse consumers, which leads us to the other direction in the fork: break clean from Symbian, develop Maemo into a refined, powerhouse smartphone platform, and push it throughout the range.

Our goal here is to test the N900, of course, but fundamentally, that's the question we tried to keep in the backs of our minds for this review: could Maemo ultimately become the platform of Nokia's future? Let's dig in.



Hardware

Your personal take on the N900's look and feel depends almost entirely on how you approach it. As a phone, it can only be described as beastly -- but as a dedicated internet device, it's one of the smaller, sexier, and more practical devices in this tweener category to come to market. Physically, anyone coming from an N810 will immediately notice what Nokia has done here -- they've essentially traded height and width for thickness, probably a fair swap now that the latest model has made the leap from a pure MID to a smartphone with MID tendencies. After all, as a phone, it has to fit in your pocket without much drama, and shaving over 17mm off the width and 12mm off the height certainly helps Nokia meet that goal.

That said, it really can't be overstated: the N900 is thick -- thick enough to put a bulge in even the loosest pocket. Carrying it around reminded us of toting our trusty N95 back in the day, and a quick lookup confirmed that they're nearly the same thickness -- the N95's actually a couple millimeters beefier, believe it or not -- so if you're used to carrying something of that girth, it could actually be a pretty smooth transition. On the other hand, owners of most modern WinMo devices, iPhones, and even Nokia's own 5800 and N97 will have more of an adjustment period.

For better or worse, the N900 carries over some very uniquely Nokia-esque elements, notably the spring-loaded slider for toggling standby mode and the power button mounted dead center along the top edge. They're complemented by a volume rocker, 3.5mm headphone jack (doubling as a TV-out), two-stage camera button, and micro-USB port along the sides. Oh, and of course, there's a stylus tucked in the corner for actuating the resistive display. It's decent -- you won't find any metal bits or mind-blowing design here (HTC typically does a better job with that), but more importantly, it's long and comfortable enough to nearly resemble a standard writing utensil.

You'll notice in the last paragraph that we refer to the right edge of the N900 as the "top" edge. That's because the device is very much landscape-oriented -- a throwback to its Internet Tablet roots and the evolution of Maemo, which predates today's trend toward full-touch handsets that are fully functional and equally usable in any orientation. We'll talk about this a bit more in the software section, but for now, bear in mind that the controls are generally placed in a way that favors landscape use.

Tearing off the back gets at another Nokia quirk -- you really do have to tear it off, like so many Nokias before this. It doesn't slide at all, you just dig your fingernail in there, pull, and hope for the best. That's fine, we suppose -- generally speaking we're uncomfortable about doing anything to our gadgets that involves tearing at a fastened cover, but as long as it's designed to do that and it doesn't break, we're cool. Underneath you've got direct access to the microSD slot, meaning that you can technically access it without pulling the battery. Speaking of the battery, it's a BL-5J, the same 1320mAh unit employed on the 5230, 5800, and X6. Underneath you'll find the SIM tray, and those three nooks and crannies are about the only reasons you've got to be in this area of the device.

Going back to the resistive display: all things considered, it's not bad at all. It's certainly not the brightest we've seen, but we found it bright enough to use in every situation we threw at it. Interestingly, we never really noticed the phone's ambient light sensor working, but maybe that's the best-case scenario for an automatic brightness adjustment mechanism -- you should never have to think about it or let it disrupt you as you use the device, as long as the screen's bright enough to read without getting blown out in dark environments. In our earlier preview of a pre-production N900, we had issues with sensitivity that we didn't seem to have here -- in all likelihood, we owe that more to the fact that we've simply re-learned how to properly use a resistive display than any material change in the final retail unit's screen. Put simply, you'll be fine here as long as you remember to stick to your fingernail and the stylus; Maemo 5's UI elements are more or less exclusively large enough to be finger-friendly, and we found the experience a good deal more satisfying than what you get with S60 5th Edition. Unless we're using a drawing app, we'd almost always prefer being able to reliably use our fingertip to a fingernail -- capacitive still wins for ease of use -- but Nokia seems to have done the best it could here.

Sliding the N900 open reveals a full QWERTY keyboard comprising three rows of well-domed keys. Unfortunately, we've seen countless better mobile keyboard designs -- we really don't have a good explanation for why Nokia did it this way. The first problem is that the N900 only slides about 40 percent of the way open, a far cry from something like the Touch Pro2 which ends up closer to 75 or 80 percent exposed in the fully locked, tilted position. That explains, in part, why they've only gone with three rows here when four gives you considerably more layout flexibility. The next issue is that the space bar is pushed all the way over to the right side, making the learning curve unnecessarily steep; the N97 and N97 Mini are both configured the same way, so we suppose Espoo has no intention of addressing this in the short term for whatever reason. For most of our time with the phone, we found ourselves typing "M" when we meant to type a space; don't get us wrong, we're certain you can get used to it, but the question is why should you have to? We weren't terribly happy with the slider mechanism itself, either; it felt beefy enough and it'll probably survive through a typical user's abuse, but it didn't have the smooth, gliding, beautifully spring-loaded response -- nor the satisfying "click" -- that you feel on many higher-end portrait QWERTY sliders these days, including Nokia's own N97.

How about battery life? 1320mAh isn't too shabby for a device of the N900's specs, but we came away with mixed results. Moderate data and light voice use while connected to both WiFi and T-Mobile 3G consistently yielded a solid day (as in a full 24 hours) for us in the States, and we were thinking that a heavy user wouldn't have much issue making it through a day -- but a second review unit connected to T-Mobile Netherlands was consistently managing about 13 hours with middling use. Of course, the N900 charges off a standard micro USB port and BL-5Js are relatively easy to find, so you've got options if you need extra juice midway through the day.

Software

Hardware aside, it's really the N900's platform -- Maemo 5 -- that has people buzzing. There are plenty of reasons to believe that what we're looking at here is a very early incarnation of what will some day be Nokia's premier smartphone operating system (regardless of whether Symbian soldiers on in emerging markets and the lower end of the mainstream), so it behooves us all to pay close attention as this thing evolves both in Nokia's labs and in the open source community where Maemo was born and raised.

The first thing, and perhaps the most prominent thing, that a user sees regardless of device or operating system is the home screen. Coming from S60 5th Edition's restrictive grid-based widget placement, you might expect some limitations on the N900 -- but you'd be wrong. In fact, the N900 has one of the most extensible, customizable home screens of any mobile device we've ever used; you can drop widgets, bookmarks, and contacts exactly where you want them right down to the pixel, and you've got a total of four panels that loop around as you swipe (unlike Android, which stops in either direction). The system works well and does a great job of maximizing the handset's available screen real estate.

Tapping the icon in the upper left takes you to the main menu (more on that in a moment) or, if you've got any apps minimized, a display that Nokia calls the "dashboard." Basically, it's yet another interpretation of the so-called "card interface" popularized by webOS, and it works well here -- you see miniaturized views of all your open applications in one place. Minimized applications smoothly glide into the grid of cards, and tapped cards smoothly glide open to full screen again -- a testament to the power of the N900's hardware, we suspect.

Beyond the home screen, system notifications are a pretty hot topic, too, considering how well Android and webOS handle them and how poorly the iPhone does by comparison. Fortunately, Maemo 5 does a pretty great job here. New text messages, emails, and the like are briefly displayed as a yellow bubble in the upper left of the display; tapping it will take you right to the source of the notification (the new SMS, for example). If you let it go, though, the notification will persist as a "card" within the N900's multitasking dashboard, taking up the same space that a normal application would. You might think this would be confusing, but it's not for a very simple reason -- notifications appear as bright yellow squares, the same color as when they first appeared. So unless you've got an app minimized here with an entirely yellow background, you won't have any confusion.

If nothing else, Maemo 5 is pretty -- Nokia's prettiest platform ever, in fact, by a wide margin. We're sure that's due in no small part to the fact that the N900 is the first in the company's Internet Tablet line to employ a modern ARM Cortex A8-based core, making screen transitions and effects fast enough to accomplish their intended function: beautify the UI without sapping away precious seconds of the user's time. Out-of-focus screen elements are actually visually out of focus, which looks great (photographers, think "nice bokeh" here) and applications zoom and fade as you open, close, and minimize them.

"Pretty" doesn't cut it, though -- at least, not without a healthy dose of usability and functionality to go along with it, and in this regard, the N900 is much, much more raw. Indeed, Nokia has been surprisingly (and wisely) forthcoming about the fact that this is not a smartphone for the masses; it's for tweakers, hackers, geeks, nerds, and people who want as much control on their handheld device as possible -- and aren't afraid to get their hands dirty in the process. In fact, we'd go so far as to say that the N900 is a proof of concept -- a reference platform for Maemo that just happens to be sold in stores. Evidence of the N900's geeky aspirations are strewn about the platform from the X Terminal icon preloaded in the main menu, to the lack of an app store at launch (more on this shortly), to the fact that you need to connect the handset to a PC and run shell commands just to perform a hard reset.

You've got UI quirkiness to contend with, too. Maemo 5 dispenses of the left-anchored taskbar present in every version of Maemo before it, and even the status bar in the upper left (where you see time, signal strength, and so on) has a tendency to disappear rather frequently, leaving you without any bearing or sense of how to navigate between apps or elements of the platform. This is most clearly evident in the main menu, where you're presented with nothing but a full page of icons -- and it's not like the N900 has a front-mounted home or back button, so to a novice user, it's anyone's guess how to back out to the home screen or move to another app that's already running. As it turns out, the answer generally is to find a blank out-of-focus area and tap on it to go back one screen, but depending on the screen you're in, that occasionally leaves you hunting for a free area on which to tap. [You can also tap along the edge of the screen -- even if the home screen icon isn't visible -- and get back. -Ed.] Worst case, you can hit the power button up top to call up the profile menu, which will bump you out to the home screen underneath -- but it's not elegant by any stretch.

Speaking of UI quirkiness, this gets back to something we touched on earlier -- the N900's almost exclusive reliance on landscape mode. We get the argument that the 770, N800, and N810 didn't have portrait mode at all, but times have changed -- people walk and surf at the same time these days (particularly with devices like the N900 that have WWAN radios on board) and it's a lot more convenient if you can do that one-handed. Portrait mode, of course, lends itself to one-handed use. If you lump this in with Maemo 5's general usability roughness, you get the sense that the platform was rushed just a bit -- Nokia took it to 90 percent and said, "hey, this is open source, let's let the community fill in the blanks." We're guessing there are plenty of buyers that are delighted with that policy, but again, these are the kinds of things that keep Nokia from having a platinum best seller on its hands. Long term, it'll be interesting to see how close Maemo 6 comes to closing that gap and making the platform accessible to consumers at large.

About the only places the N900 officially supports portrait mode at this point are the Phone and Photos apps; you can hack it into the browser right now and we suspect the rest of the platform will get there soon enough, but we digress. In fact, you have to use the Phone app in portrait -- there aren't any apps in the device's standard load that support automatic orientation. [Turns out you can, you just need the keyboard open! -Ed.] It's a little weird, but we're thankful in at least one regard: the phone is the one piece of software here that absolutely, positively must be ready to use in portrait, particularly considering that the earpiece is at one end. As a phone, the N900's pretty basic -- again, Nokia considers this a MID with a phone bolted on, not the other way around -- but you get a finger-friendly keypad and full contact integration, which works swimmingly when paired with something like Google Sync (it totally works in the latest N900 firmware, by the way).

There is one key area where the N900's phone excels, though: Skype support. In fact, this is about the best Skype experience we've ever had on a mobile phone -- you add your account through the N900's control panel, which then keeps you connected and ready to take and place VoIP calls just as you would a GSM call. It's truly seamless and worked extraordinarily well. In fact, there was a point when we were on a GSM call and a Skype call came through on call waiting, which we could switch to and place the original caller on hold -- had we not known the caller was on Skype ahead of time, we wouldn't have been able to tell. Likewise, you can natively add contacts' Skype IDs in the address book. Ironically, the whole integration makes the N900 the closest the Internet Tablet series has ever been to not needing a GSM radio -- and yet it's the first to have one.

The N900 includes a Maemo build of Ovi Maps, a staple for most Nokia handsets sold today. Coming from Google Maps on Android and iPhone, Ovi Maps leaves a lot to be desired here. First up -- and this isn't Ovi Maps' fault, specifically -- we had an awful time with AGPS, which was totally unable to get even a rough lock without GPS line of sight. At this point, we're used to living in the world of instant location mapping that Google has brought to every platform that Google Maps has touched, and we really miss it here -- waiting for a satellite constellation is so 2005. As for the app itself, it's on par with something you might expect a couple years ago; it can map routes (and the latest firmware is supposed to speed that process substantially), but you don't have turn-by-turn navigation or cool add-ons like street view out of the box. Finally, map scrolling is one activity that's made measurably easier on a capacitive screen -- preferably with multitouch -- so no amount of user hacking or third-party development is going to fix that particular issue. On the plus side, the map renders quite quickly as you scroll (everything we tested on the N900 moved with hustle, really) and we appreciated the app's shortcuts for bouncing between common zoom levels (country, city, and so on).

Speaking of Ovi, how about the Ovi Store? We just had a little bit of time to play with the live beta of Nokia's Maemo port of the Store which went live shortly before this review, and at this point, it's a little undercooked (hence the "beta" label, we suppose). The most glaring deficiency is in the usability of the UI; rather than make an actual Ovi Store app, Nokia has elected to simply point users to a mobile-optimized portal in the browser, which ultimately leads to more scrolling and tapping than you'd like. That's not the end of the world, though; the bigger problem in the short term is the availability of actual... you know, apps. We searched for a few common phrases ("IRC," for example) and were met with zero results; in all, the store has fewer than 100 assets as of press time, and many of those are images, videos, and themes rather than actual applications. Over the years, Internet Tablet users have grown accustomed to getting their free, open wares over both official and unofficial repositories, and injecting the Ovi Store's layer of commercialism in there is a new step that might not gel at first with folks upgrading from N800s and N810s -- that said, it's an absolutely vital step to taking Maemo mainstream, so we hope Nokia finds some creative ways to attract more high-profile devs to the platform.

Now, finally, let's talk about this handset's real treat, its crown jewel: the glorious browser. The Internet Tablet line has used a fairly capable Mozilla-based browser for ages, but between the latest tweaked code and the N900's thoroughly freshened internals, it's gone to an entirely new level. Almost without fail, sites were rendered faithfully (just as you'd expect them to look in Firefox on your desktop) with fully-functional, usable Flash embeds -- and it's fast. Not only is the initial rendering fast, but scrolling around complex pages (Engadget's always a good example) was effortless; you see the typical grid pattern when you first scroll into a new area, of course, but it fills in with the correct content rapidly. To say we were blown away by the N900's raw browsing power would be an understatement -- in fact, we could realistically see carrying it in addition to another phone for browsing alone, because even in areas where it gives a little ground to the iPhone or Pre in usability, it smacks everyone down in raw power and compatibility. In our line of work where 24 / 7 access to the web is of paramount importance, having the N900 in our pocket when we were away from our laptop was a comforting insurance policy. As with Ovi Maps, the one complaint we'd lodge here is that capacitive multitouch would've been a huge win, but we adopted to the resistive setup without too much drama -- and the inclusion of a creative "swirl to zoom" gesture certainly mitigates the problem. Just don't lose the stylus!

Wrap-up

We came into this review wanting to know as much about Maemo as a platform as we did about the N900 itself; after all, the N900's just a single phone that'll be dead and forgotten from store shelves within a year. That's just reality, the hustle-and-bustle pace of the modern handset release cycle. Maemo, however, will live on -- but in what capacity? Where does it fit (or could it fit) in Nokia's grand plan?

After having dug in, we're seeing glimmers of brilliance here that give us hope. Maemo 5 isn't the polished, consumer-friendly, all-encompassing solution that Palm, Google, and Apple are all selling today, but it's fairly evident that Nokia has built itself a stable, extensible platform that can reach those levels with a little tender loving care. The company's commitment to open source and the Maemo development community is commendable -- it's something that should absolutely continue -- but going forward, we'd love to see what kinds of magical things could happen if it took development to 100 percent feature completion internally with a full round of usability testing before handing it off to the eager geeks in the field. The mere thought sends shivers down our spine.

That said, for now, Maemo officially remains an experiment; there's no greater evidence of that than the N900's half-bakedness. And hey, calling the N900 half-baked seriously isn't a knock in this case -- it's just a realistic admission of where Maemo stands today. As it has with its predecessors, Nokia seems totally comfortable with that assessment, throwing this loosely-assembled box of high-power hardware and software at anyone who dares live on the bleeding mobile edge. The company continues to insist that Symbian has a huge place in its line and will continue to do so, but long-term, we see nothing about Maemo that leads us to believe it couldn't be Nokia's single platform of the future. Even if it takes high-end hardware to run effectively, you can't deny that today's high-end is inevitably tomorrow's low-end. Everything gets cheaper, and Maemo itself -- by its very nature -- is free for Nokia to distribute.

Let's turn our attention back to the N900, though, since it's the only Maemo 5-powered device available today. Is it a keeper? As a daily workhorse smartphone for your average Jill or Joe, it's impossible to recommend the N900 at this point; it's just missing too much functionality that's waiting to be written by some enterprising CS grad students with spare time on their hands. As a second, dedicated browsing device or a geeky weekend hobby, though -- possibly an upgrade from an N810 -- the N900 is a very compelling device indeed, as long as you remember one simple rule: it's a computer with a phone, not a phone that can compute.

Additional reporting by Thomas Ricker
engadget.com
Share:

Motorola DROID review

It's hard to look at the DROID without looking at the company which brought the device to life. Motorola: for years the name has been synonymous with... well, disappointment. While the industry-stalwart made cellphones sexy with the RAZR, the days which followed have not been especially fruitful or compelling. Over the past year or so, we've seen Motorola beating its way back into the mainstream through a series of smart plays: first embracing Android as a platform, then shucking off the weight of Windows Mobile and finally bringing some desirable (and high profile) devices to market.

With the DROID, the company has perhaps created its most attractive and intriguing piece of technology yet. Forging an alliance with both Verizon and Google, Motorola has come up with a second compelling reason to count the phonemaker down, but certainly not out, while the other two giants have finally found a seemingly worthy device to position against the iPhone. So we must pose these questions: is this the phone which will catapult Android into the mainstream? Is it the device that will pull Motorola back from the brink? And -- most importantly -- is it the lynchpin Google and Verizon have needed to challenge the leader in mindshare in the smartphone market? After putting the device through its paces, we think we can give you the answers you seek -- so read on to find out!


Hardware


The DROID is an odd and beautiful device. Looking at the hardware from a purely philosophical standpoint, the ID of the phone seems staunchly defiant. Instead of taking its cues (and lines) from current contenders in the smartphone space, the DROID is all hard edges and angular slopes. The construction is a mix of plastic and metal, and the phone has a solid, expensive heft to it. Couple that weight with soft touch materials and gold highlights, and the effect is somewhere halfway between a Vertu device and the European version of the Hero -- and it's a good mix.

The basic structure of the phone is made up of two main pieces, the large, glass display up top, and the slightly longer keyboard / mainboard lower half. Above, the 3.7-inch screen dominates, almost filling the space edge-to-edge, though there are four capacitive buttons at the bottom of the display: back, menu, home, and search (which might be tricky for folks coming from other Android devices, since they've thrown the order of the buttons in the blender). The top section slides smoothly upwards to reveal the aforementioned QWERTY keyboard, though unlike other models of this ilk, it doesn't snap automatically into place; rather, it requires a bit of force to move up, then clicks firmly once settled. The keyboard is a wide (though mostly flush) affair, with minimal amount of spacing between the keys. To the right of the four row QWERTY is a 5-way rocker -- a bizarre deviation from the CLIQ's left-sided controls -- and the bottom piece has a strip which juts out from the device with a small mic hole (closed or open). It's almost like Motorola's version of the HTC chin... though tempered somewhat. Atop the phone is a 3.5mm headphone jack and a power / sleep button; along the right edge is a volume rocker, and camera button on opposite ends; the left side houses a MicroUSB port; around back the 5 megapixel camera (and flash) are revealed, along with a thin, gold, crosshatch strip that hides the DROID's speaker.


The thickness of the DROID is striking, coming in at just a hair (13.7mm vs 12.33mm) thicker than the iPhone 3GS. The body itself is actually narrower than the iPhone. While thinness is important (though typically not a deal breaker for us), the fact that the phone packs a larger, higher resolution screen and a physical keyboard in such a small frame is notable.

In all, Motorola has pulled off what seemed unimaginable for them just 12 months ago; they've made a device which is truly lustworthy, even next to the best efforts of Apple, HTC, and Palm.

Internals

Inside the DROID beats an Arm Cortex A8 CPU (a 600MHz, OMAP3430 chip downclocked to 550MHz), 256MB of RAM, and 512MB of ROM. If that CPU sounds familiar, it should -- it's similar to the chip inside the iPhone 3GS and Palm Pre. If you're wondering about performance, you can breathe a sigh of relief... kind of. Yes, there is a noticeable bump in speed when switching applications on the phone, scrolling through lists, and generally getting any basic tasks done. We did notice, however, that paging through homescreens on the DROID actually seemed somewhat stuttery; odd, considering this phone is certainly better equipped than most Android devices to handle pixel pushing. Pulling down the window shade notification area also seemed less than optimal. We don't know if this was due to the screen resolution being jacked up, or just a software quirk, but it was mildly disheartening -- especially considering that the rest of the phone's performance seemed extra snappy to us. As an aside, in a totally unscientific test of playing a 3D game (Mystique, in case you're wondering) the rendering seemed considerably smoother on the DROID than with other, older Android-based phones we've used.

Throughout our tests, we were consistently impressed with the tightness and speed of navigation on the phone. The DROID makes Android feel modern the way the iPhone 3GS and Palm Pre are -- like machines designed for a pace of life that's increasingly more Twitter and less USPS.

Display


As we mentioned, the screen on the DROID is a 3.7-inch capacitive touchscreen -- a full glass display with a WVGA resolution clocking in at a handsome 480 x 854. We found the responsiveness on the DROID to be on par (if not better) than most of its Android contemporaries; gestures and flicks registered with little to no lag. Whether that can be attributed to Moto's screen technology, Android 2.0 improvements, or just the speedy CPU inside the DROID is anyone's guess, but we certainly won't knock the phone for it. Another perk to having that big screen is seeing webpages how they're meant to be viewed (or at least closer), and browsing on the DROID is a solid experience. Those additional pixels definitely come in handy when you're looking at something graphically intensive or wordy... such as Engadget.

As you have probably heard (or guessed), there's no multitouch on this device. That's clearly an issue with Android 2.0 and choices that Google is making about user interface -- we're fairly certain there's nothing technically holding back the DROID from utilizing multitouch input, and we wouldn't be surprised to see some tweaked ROMs hit the information superhighway with the functionality onboard. Regardless, the resolution, materials, and clarity of the DROID display make it an absolute pleasure to keep your eyes on. Motorola gets a +1 for the bump in resolution, and we can only hope everyone else follows suit.

Note: Android 2.0 does support multitouch events, but the functionality isn't implemented here.

Keyboard


A physical keyboard can be a blessing or a curse, depending on just how well (or poorly) it performs. In the case of Android devices, QWERTYs have definitely been hit or miss. We think the closest case for comparison with the DROID's version would be the G1; both have shallow, clicky keys, and both force your right hand into a bit of an awkward position. On the G1, it's due to the placement of the "chin," and with the DROID, it's all down to the five-way rocker living next to the 'board itself. We're happy to report, however, that after a short adjustment period, typing on the DROID is a reasonable experience. It's not as slick or comfortable as a nice, portrait-oriented Tour or (better yet) Bold layout, though it bests the CLIQ, and holds its own against other landscape contenders like the Moment.

Visually, the keyboard is an easier read (and more aesthetically pleasing) than those other QWERTY phones too, though sometimes the keys can feel a bit cramped. Additionally, we had major issues with the auto-dimming on the DROID. If we left the screen in auto brightness mode, the constant on / off dimming of the keyboard was intolerable; eventually we had to just switch the auto dim off altogether. We also had issues with the keyboard not lighting up at all in some instances, requiring us to close and open the pad again. Not a huge deal, but annoying when you're trying to quickly tap out a message. Admittedly, we missed the CLIQ's two-stage keyboard backlighting that only enabled the second light when ALT was pressed, but it's a luxury we can do without.

As you would expect, Android 2.0 includes the onscreen keyboard as well, but there don't seem to be many improvements in this area. As a backup keyboard for quick SMSs and the like, it works, though we eventually had to replace it with the Better Keyboard application -- which we think is more usable and snappier. In comparison to the iPhone keyboard (really the high bar for virtual keys) Android continues to feel like a distant second. Still, you won't go to it that much -- the DROID's physical keyboard is solid, but it's going to take some getting used to for most people.

Camera


Google has made some pretty major changes to the camera application in Android 2.0 (including more control over white balance, focal length, flash settings, and effects), and Motorola has smartly outfitted the DROID with a 5 megapixel camera coupled with an LED flash. It sounds like a match made in heaven, right? Well, not quite.


No, no, no. Yes! Our attempts to photograph a watch in broad daylight.

While the camera certainly seems capable of taking great looking photos, getting everything to play nice isn't as easy as it should be. First off, the camera is painfully slow to focus and snap pictures -- and when it does, the results can be unpredictable. Strangely, the lens seems to be able to take pretty sharp macro photos (it's even a setting in the camera app), but it struggled with getting adjusted to close subjects, even in broad daylight. Sometimes we got lucky and cranked out a decent pic, but the process was frustrating. Furthermore, the new settings Google has added to 2.0 are contained in a hard to get to and counterintuitive menu which sits to the left of your viewing area. Trying to make changes on the fly was a hassle. If this is the best the engineers at Google can do, they need to outsource this work.


Video, on the other hand, was somewhat of a pleasant surprise. The DROID is capable of shooting at a 720 x 480 resolution, and in our tests, produced watchable -- if not totally shake-free -- video. The phone definitely fares better in this department than with stills, and we could easily see using the DROID as a stand-in for a flip cam. You can check out a little of the action in the video below (with a surprise cameo from !!!'s Nic Offer).


Speaker / earpiece


The sound on the DROID is second to none -- really. In fact, this is simply one of the best sounding devices we've ever used. Whether it's audio through the loud (but undistorted) earpiece, or a speakerphone call -- even music -- the sound which Motorola's device outputs is crystal clear. Now, obviously Verizon's reception has something to do with our in-call sound, but it's likely Moto put some thought into the aural aspect of the phone. There's not really much to say except that we were more than pleased with the audio fidelity of the DROID, and we can only hope that future phone makers (ahem, Apple) look to this device as a high water mark in this department.

Software


Besides the introduction of the phone itself, obviously 2.0 is a major update for Android. Based on the launch and hype surrounding Moto's device, we'd say it's fair to assume that Google wanted as many eyes on the achievement as possible. They definitely got it with the DROID -- but was it worth all the fuss?

The first thing you should know is that Android 2.0 isn't drastically different than 1.5 or 1.6, save for a few notable features and tweaks that have significant impact. True to form, Google hasn't gone for visual flair or wild embellishments for the sake of a few dropped jaws; most of these changes are about functionality and usability.

One of the first major changes Google has made is support for multiple Gmail or Exchange accounts, and a new universal inbox which allows you to get a look at your electronic correspondences in a single view. For BlackBerry users, this concept is old hat, but for most people with multiple accounts, it should feel like manna from heaven. We would have been slightly more stoked about the feature if it allowed you to look at both Gmail and POP / IMAP / Exchange accounts in one field. Instead, you can view your Gmail accounts separately (not in a single stream, but in one place), and your other accounts can be blended in the "Combined Inbox" view. Not exactly a perfect implementation for those of us with both Exchange and Google accounts, but certainly a solution light years beyond what previous versions of Android were offering. Another minor niggle: deleting an email now takes you to the next email in your inbox rather than bumping you back out to the list of emails, as it did in 1.5 and 1.6. We preferred the old functionality, though we imagine some will prefer the new as well.

We loved being able to keep a few of our accounts in the phone, but we ran into a weird and annoying issue when attempting to remove one of them. We were using the DROID with two Gmail accounts active, but when we tried to remove the second one we'd added (note: not the account we used for our contacts or calendars) the device informed us that we would need to factory reset the phone because that account was "required" for certain applications. Try as we might, we couldn't find a way around the problem, and we eventually did reset the device. The behavior was strange to say the least, especially since it was a barely-used, secondary account -- not a daily use address which tied into services.

As you may have heard, Facebook account integration is now built into 2.0, and there should be more of that coming, as Google has created "sync adapters" which allow third parties to plug into the contact and calendars of your phone. Mercifully, Google has figure out that you might not want your Facebook contacts in your address book, and gives you the option to turn off contact syncing (as it does with Exchange and Gmail accounts). You're also given the option to sync contacts, but keep certain sets from displaying in your contacts list; this variation is best demonstrated with Facebook integration, because it merges duplicate names and pulls the accompanying images, but doesn't clutter up your Gmail contacts with additional names. Beyond that, the pairing doesn't go tremendously deep, even though we're told Facebook had a hand in this version of the OS as well. Really, you get a widget for your homescreen which auto-updates, and that contact integration if you really want it. This is obviously just the tip of the iceberg for this kind of... er, synergy, and we expect to see lots of people taking advantage of the feature (hello, Twitter). Regardless, it's a forward thinking move that will clearly obviate the need for some of the functionality built into BLUR, and makes the DROID (and other 2.0 phones) competitive against the Pre and Pixi when it comes to social networking integration.

Speaking of contacts, Google has made some big and thoughtful changes to how contacts are handled (and used) in Android 2.0, most notably adding a "Quick Contact" menu to your contact list. The quick contact function allows you to tap on someone's name and get a context menu with jumps to the various ways you can reach out; if you're friends with someone on Facebook, you'll be given an option to message them there, along with SMS, phone, and email choices. It's a brilliant little touch that makes quickly pinging someone a cinch. Android 2.0 also improves the SMS and MMS experience by giving you the option to search your messages, and also allowing you to set a limit on how many SMSs to store before beginning to delete old threads. It's not groundbreaking stuff, but nice choices to have (finally).


You'll notice some major changes within the browser, most notably the fact that when you load up pages now, you're presented with a fully zoomed-out "overview" (much like the iPhone and Pre). If you've been griping about that weird, half-zoom that Android has relied on for so long (as we have), this is a breath of fresh air. Coupled with the DROID's massive display, it makes navigating pages roughly a million times more pleasant. The updated browser also now supports double-taps to zoom (as does Google Maps) -- making navigation a bit more natural -- though we noticed some weird column display issues on our site and others. As we mentioned before, there's still no multitouch, but this does stand in quite well for pinch zooming. While the overall browser speed still isn't as snappy as the iPhone 3GS (or even the Pre), it's a step up from previous efforts, and when you factor in little touches like auto-prediction on URL entry, it's eminently usable.

As we said, most of the alterations are under the hood -- not stuff that immediately jumps out at you, though there are some notable visual tweaks which bear mentioning. Google has added some new fades and cross-application animations into 2.0 which makes Android seem a bit more contemporary. Of course, older iterations of Android contained animations, but 2.0 seems far more polished to our eyes. Additionally, icons and elements have been updated across the board to give the OS a more modern look, sadly there is much of this UI and its applications that remain unchanged -- and not for the better.


A few of the obvious spots include the music player, which is quite frankly a mess; not only is the navigation poorly thought out, but the application is just straight-up ugly. It's not easy on the eyes, and not much fun to use either. The same goes for the phone app -- the remnants of a hastily thrown together interface are plain here, and the functionality of the phone itself gave us some issues. Often the screen was confused or unresponsive during calls, as if the hardware and software weren't communicating with each other properly. It seems obvious to us that some portions of Android need a serious, ground-up reworking... but they don't get them here. Another annoyance was the home screen -- unlike with HTC's tweaks (or even Motorola's BLUR), you only get three screens for icons and widgets. Furthermore, the DROID doesn't come equipped with even the most basic widgets you see in most new builds, like weather. The weird thing is that there is a weather app in the dock display, but no way to access the application in standard phone mode.

Additionally, some third-party (and even some first-party) software seems unable to deal with the DROID's new resolution. There are bitmaps that look upscaled and jagged, such as the attachment icon in Gmail. The game Robo Defense seemed to play slower than it did on the Hero, which was a bit of a surprise, though it has been updated to support the new resolution. None of these problems are show stoppers, but it points to a disconnect between where Google is at versus its developers. There is catch-up to be played.

Also notable (and perhaps a selling point for some) is that the DROID is a Google Experience device, which should theoretically mean that it's more likely to receive fast and frequent software updates than its skinned cousins like the CLIQ. The Google Experience is sort of the "gold standard" Android showcase for the company, so to speak, and it's in Google's best interest to keep it rock solid at all times -- and since there's no third-party skin to revalidate after every Android version is released, the update process should go a heck of a lot smoother.

One thing to keep in mind: when it comes to media syncing, you're in the same boat you were for previous versions of Android -- which means sideloading or additional desktop apps. doubleTwist has just introduced DROID compatibility, though the experience leaves much to be desired. In fact, after our tests, we'd say you're better off just mounting that SD card and dragging your content over.


Navigation


One of the biggest pieces of news (perhaps the biggest) to come out of the DROID launch was the introduction of dedicated, fully realized turn-by-turn navigation which integrates with Google Maps. The DROID makes further use of this functionality by switching into a nav mode when snapped into a dock (you can also enter the application normally, sans dock). Google has gone all out on this, providing a rich mixture of its satellite, map, traffic, and location info with text-to-speech directions. Of course, the big G takes it one step further and adds layers like parking info, ATM spots, restaurants, and gas station locations (amongst others) to the stew, making the navigation more robust than many dedicated PNDs -- which would explain that nasty drop in Garmin and TomTom stock we saw yesterday.

In our tests, the nav worked excellently for the most part, though as you can see in the video above, we did run into some minor issues on our hunt for cannoli. It's not uncommon for a GPS unit to send you the wrong way down a one way street, and maybe it was just unlucky coincidence that it happened on our first outing, but being told to turn left where you can't -- then being sent in a loop -- doesn't fill us with warm, fuzzy sensations. Still, the navigation is super intuitive and cleanly laid out, and even if there were major issues (which there really aren't), it's hard to knock a service that is completely free. We think a little more time and some longer trips will help put it in better perspective, but we like what we've seen so far.

Accessories


The DROID will get a few nifty extras when it launches, most notably a dock for setting your phone on a nightstand (or appropriate flat surface), and a car mount for using the device as a proper GPS unit. Both are notable because they use sensors to alter the DROID's functionality. The dock turns the DROID into something that looks not entirely dissimilar from Verizon's now defunct Hub, while the car mount just boots the phone into nav mode. Both are nice touches, and you'll want the car mount if you plan on taking Google up on that offer of free satnav.

Battery life


We haven't had a lot of time to put the DROID through its paces when it comes to battery life, but at a glance it seems to be holding its own against the current crop of 3G devices -- impressive considering it's only packing a 1400mAh battery behind that extremely sexy door. Paul Miller, who has been concurrently testing the phone, claims he had 24 hours of on and off usage before requiring a recharge (syncing, but no major phone calls or lots of screen time). In general, you won't be blown away by the DROID's staying power, but it doesn't deviate in any wild ways which should make you take pause. It's solid, not breathtaking, and it seems better than the CLIQ, which -- despite using the same battery -- typically manages to just barely eke through a day's worth of typical use.

Wrap-up


It will be difficult for casual observers not to see the DROID as a kind of anti-iPhone in Verizon's arsenal. Certainly the company has played up the comparison with its "DROID does" ad campaign, and it's no secret that Verizon and Apple have previously had some friction -- the V famously passed on the first-generation iPhone, after all. Of course, it's easy to draw parallels between the two devices; as with most current smartphones, they share a tremendous number of similarities, though there is plenty that set the two apart as well. And that's really kind of the point -- it's useless to look at devices like this in black and white, or to try and figure out if an Android device on Verizon is better than an Apple device on AT&T (or any other device on any other carrier, for that matter). What it ultimately comes down to when judging this kind of device is more complicated than a "yes" or "no" answer.

If you must compare the DROID to the iPhone, then know that the Android platform still has a ways to go before the experience of using the phone is as seamless as the one Apple has created -- but also know that Apple has a long way to go before its messaging, email, and customization can match what Google is offering. Both products have very distinct strengths and weaknesses.

So, is the DROID a good smartphone? Yes, the DROID is an excellent smartphone with many (if not all) of the features that a modern user would expect, and if you're a Verizon customer, there probably isn't a more action packed device on the network. That's not to say the device doesn't have its faults; the camera was unpleasant to use, the application selection feels thin in both quantity and quality (despite the claim of 10,000 options), and the phone has bits of basic, non-intuitive functionality that might chafe on some users after a while. But even still, it's hard not to recommend the DROID to potential buyers eager to do more with their devices. It's easily the best Android phone to date, and when you couple the revamped OS, Verizon's killer network, and an industrial design straight from a gadget enthusiast's fever-dream, it makes for a powerful concoction. Ultimately, the DROID won't usurp the iPhone from the public's collective mindshare or convince casual users that they must switch to Android, but it will make a lot of serious geeks seriously happy -- and that's good enough for us.

engadget.com
Share:

Support

Definition List