Just like the other Droids, this model’s slider lacks any spring assistance, instead it slides out along a friction-guided two-rail track. It’s pretty obvious where that friction happens and where the slider locks into the display part, given the two small notches at the top, and likewise where the tracks are at the extreme left and right. Initially I found the Droid 3 slider a bit resistive and not super smooth, however after a few days of use it settled into a much better and smoother groove.

It still isn’t quite as fluid as HTC’s latest designs, but again gets the job done with an impressive thickness (or lack thereof). The back of the display is topped with a reflective, patterned surface which also unfortunately collects fingerprints.

So how is the keyboard that the slider makes possible? In a word - amazing. Yes, it quite literally is the closest to perfect I’ve seen in a very long time. Each iteration of Motorola Droid keyboards has gotten slightly better, starting with the almost unusable Droid 1’s concave keys which had minimal feedback, to the mid-cycle refresh which changed key domes to convex, followed up by the Droid 2 which removed the D-pad and improved communication, and now the Droid 3.

The Droid 3 adds a fifth keyboard row, this time dedicated exclusively to the arabic numerals. I originally thought having numerics wouldn’t make much sense, but after entering my 20-character WPA PSK for probably the hundredth time followed by the usual assortment of passwords for email and google accounts, it finally made sense. Having a row dedicated to numerics just makes so much sense in retrospect, both for entering phone numbers in messaging, passwords, and so many other situations.

The numerical row also does double duty by acting as a buffer between the top row of the latin characters and the top display slider. My only major complaint with the Droid 2 and before was that there was very little space between this top row and the display slider - if you had any fingernails at all or even just large fingers, they’d likely collide with that slider when typing on the top row. Now, having one more (even half height) row makes that a solved problem.

The keys on the Droid 2 previously had little space between them, it was primarily one large piece without a discrete gap between characters. The Droid 3 now includes a shiny plastic layer between keys, which will no doubt show lots of grime in due time, but it does make each key independently clicky.

The only rearrangements to speak of are the removal of alt-lock and the back keys, and repositioning of the tab key. The bottom row also is slightly shifted to the left. Material and tactile feel on these new domes are excellent. Again, the keys are convex, topped in a soft matte texture, and communicatively clicky. Motorola takes a nod from Apple with a caps-lock indicator that nicely disappears into the lip on the left next to the shift key - it’s a nice touch which makes the caps lock indicator visible even with a finger on the button.

Backlighting on the Droid 3 keyboard is nice and even. There aren’t any controls in settings for controlling when the backlight comes on or how long until it turns off. Backlighting seems to turn on and remain on when ambient brightness is under a certain level. Alongside the Droid 2, the Droid 3 seems very conservative with its keyboard backlighting, as it seems to enable it at a notably lower ambient light level than its predecessor.

The capacitive buttons are likewise backlit the same way they have been on previous Motorola Droids, and thankfully the order of these respective Android keys are unchanged from the Droid 2 to 3. There’s a bit of capacitive button backlight bleed at the bottom of the display where the glass ends and meets plastic, but it isn’t too distracting.

 

Since we’ve been talking about the keyboard, I think it’s worth mentioning that the Droid 3 continues the Motorola legacy of including a host of software keyboard options for portrait view. Swype, the default Motorola multi-touch keyboard, and the Android 2.3 stock gingerbread keyboard are all preinstalled an available as options. I’m glad the Droid 3 doesn’t do away with the gingerbread keyboard, like I’ve seen other Android 2.3.x handsets do. Swype is themed to look like Motoblur, and the multi-touch keyboard is as good as it always has been on other Motorola Android devices.

The last part is that there’s another pane in the input and keyboards settings page for the hardware keyboard with a few options. What feels neglected is how anemic the hardware keyboard auto-replace engine is. Compared with the gingerbread and even Motorola multi-touch keyboards, the hardware keyboard has an almost non-existant auto-replace engine for fixing misspelled words. In practice, it does little more than correct things like “im” to “I’m,” and so forth. It’d be nice to see the hardware keyboard get a bit more love.

Hardware Overview - Nods from the Droid X Droid 3 Car Dock
Comments Locked

84 Comments

View All Comments

  • RoninX - Sunday, July 31, 2011 - link

    I'm guessing that people who prefer a physical keyboard (like myself) would rather manually correct spelling errors than deal with <a href="http://damnyouautocorrect.com/">overly aggressive autocorrect algorithms</a>.

    I currently have a Droid 2 on a one-year contract that's eligible for an upgrade, and I'm strongly learning toward getting a Droid 3, due largely to the excellent keyboard.

    I'll have to see the Pentile screen in-person before making a decision. I find it interesting that some people find the Pentile effect imperceptible, while others find it unbearable.

    I'm also curious about the Samsung <a href="http://www.bgr.com/2011/07/29/atts-sleek-samsung-s... which looks like a dual-core Exynos slider. The keyboard doesn't look nearly as good as the Droid 3's, but the 3000+ score on Quadrant (similar to the SGS2) is intriguing...
  • RoninX - Sunday, July 31, 2011 - link

    That should read, the Samsung http://www.bgr.com/2011/07/29/atts-sleek-samsung-s...">SCH-i927 dual-core Exynos slider.
  • hackbod - Monday, August 1, 2011 - link

    Auto-correcting input from a hard keyboard is actually very different than from a soft keyboard. A soft keyboard's auto correction is deeply tied to the key layout, and tables built to map specific tap positions on the keyboard to the possible letters that may be intended.

    The Android IME architecture *does* allow the IME to perform the same kinds of text processing operations on physical keyboard input as it does on touch input. However, in practice, a soft keyboard IME is designed around processing touch input, and you probably wouldn't want it to do the same processing of hard key input because the result would be poor.
  • jvchapman - Saturday, July 30, 2011 - link

    No 4G = Useless.
  • bjacobson - Saturday, July 30, 2011 - link

    looks like the display is still sunken down under the gorilla glass like on the Droid1 and Droid2? The more I use others' phones (Samsung Galaxy, Iphone, etc) the more it bugs me on mine...significantly increases glare.
  • bjacobson - Saturday, July 30, 2011 - link

    The dragging down notifications bar animation, on all the OMAP based phones I played with, runs at 20-30 FPS best case.

    The Samsung Galaxy animation for it is much smoother for whatever reason.

    This is the biggest beef I have with android phones; I play with my friend's Iphone 3gs and it's still smoother than the latest android hardware...
  • Mumrik - Saturday, July 30, 2011 - link

    I really don't get why we have to have those sucky touch buttons under the screen when they could be proper physical buttons.
  • Myrandex - Monday, August 1, 2011 - link

    I agree. I miss call start and end buttons personally.

    Jason Cook
  • anandtech pirate - Saturday, July 30, 2011 - link

    only 512mb of ram? I'm sure throwing in another 512mb wouldn't have added much to the cost. and I bet the performance boost would have been worth it.

    also..... whatever happened to the evo3D review?.... just wondering like a lot of other people
  • tipoo - Saturday, July 30, 2011 - link

    Does anything indicate 512MB currently bottlenecks Android or its apps? We just moved away from 256MB not so long ago, after all.

Log in

Don't have an account? Sign up now