If that opening paragraph sounds a little too much like I’ve been drinking the ‘wearables Kool-Aid’ then don’t worry on two accounts. Firstly, no one will need a smartwatch – even after intensive testing I’d only rate it as a ‘convenience’, something that helps and is ‘jolly nice to have’. Not to mention downright ‘cool’ and ‘fun’. But certainly not essential – your phone is the bit you really, really need. Secondly, I went into testing Android Wear as a sceptic, just like (possibly) you. But the more I used it, the more I liked the interface, the more I could see where Google were going with Android 4, with Google Now and, now, finally, with Android Wear. It really is all coming together, even if we don’t have a holistically ‘kick-ass’ solution just yet. Give it time.

Hardware

The LG G Watch, however, isn’t exactly ‘kick-ass’, in terms of implementation. It’s competently made in steel, plastic and glass, but it’s hard to fall in love with the square, boxy design and low grade backlit LCD screen. The former always feels bulky and somewhat awkward on the wrist, with no hint of style, while the latter looks pretty enough indoors but is unreadable outdoors when the sun’s shining (on default brightness – you’ll see here that Rita partly solved this by cranking the brightness up manually – at the expense of halving the already poor battery life!) This is typical behaviour for cheap LCD screens, by the way – budget Android smartphones have these and exactly the same issues. The LG G Watch currently retails for about £150 (in the UK), but most of this is going to reward LG for its R&D – the physical hardware is much, much cheaper than this and I’ll lay odds that the G Watch is half the price within six months. But, again, don’t take these criticisms as showstoppers because the whole point of the gadget is that it’s letting you play with tomorrow’s (ok, ok, next year’s) technology today, in the form of Android Wear, effectively surfacing quite a bit of the functionality of your smartphone through a couple of square inches of screen on your wrist.

Interface

The interface is deliberately kept simple by Google:

A standby screen, always on (by default), showing time and number of ‘steps’ taken today (unless another notification is deemed to take precedence – in the example above, the current cricket test score is summarised). On the G Watch, this is implemented on the LCD screen with minimal graphics and the backlight on quite a low setting. You can turn the ‘always on’ display off in the G Watch’s settings, but the device is then blank until you tap it, rather foiling the point of the time-telling functionality! Tap the standby screen and you get a backlit, colourful homescreen, with picturesque, randomly chosen backgrounds (usually landscapes of some kind, pre-loaded by LG or Google) and at least one part of one ‘card’. Cards can be thought of in the same way as Google Now cards – facts or reminders in glanceable form – and you can swipe up or down to move between the various cards on offer. Swiping down gently from the top lets you ‘peek’ at the date and battery status, and, swiping down further, toggles the ‘Mute’/’Unmute’ status of the device. Tapping the background or saying “OK Google” will, assuming your Bluetooth-connected smartphone is hooked up to the Internet, provide the same voice interface as the phone. So you can ask questions, issue basic instructions, and so on – all the stuff you’ve played with in Android for the last year or so. Great fun, and often genuinely useful as well, especially when your hands are otherwise busy, for example when driving – sending out a text to someone or asking for navigation instructions to a destination are easy to accomplish. Voice control/querying by the Google Search system built into Android Wear… Swiping right on an Android Wear card dismisses it, as you’d see on the phone in Google Now. Swiping left takes you, if appropriate, to a more detailed view of whatever’s on the card. For a text message you’d see more of the content of the SMS, for a flight boarding card, you’d see the QR code that could be scanned by the airline staff, and so on. Detailed view within an Android Wear card, here showing a flight boarding card QR code Swiping left again delves one more layer into the information, for example, with passenger details in the boarding card example, and for many cards, swiping left again takes you to a ‘Open on phone’ graphic, the sign that the smartwatch is out of display options and that you’ll need to open up your phone instead. Tap this graphic and the right application and data are launched in Android on the handset. Finally, on the “OK Google” voice recognition screen, there’s a swipeable main menu for the watch, showing the functions which are built-in, along with Settings and any third party watch applications that you’ve sideloaded from Android Wear on your phone.

The interface is surprisingly useful – touch control on a tiny watch screen is never going to be optimal, but Google has done a good job and, most of the time, accurate tapping is not required – it’s all done with voice and ‘swipes’, which are easier to accomplish when on the move. The interface is also surprisingly colourful, with Android Wear selecting appropriate backgrounds for each card – again, returning to the flight boarding card example, a graphic of an airliner climbing into a dark blue starry sky is used. Or a cityscape behind a public transport notification. You get the idea. It’s all pleasant, well thought out on the whole and very… Google.

Applications and real world use

Third party applications, which are just starting to appear, can be launched with (e.g.) “Start Keep” (to run ‘Google Keep’), though starting actual applications (as opposed to the running core Android Wear OS) definitely show the hardware’s limitations, with even simple apps sometimes taking four or five seconds to crank into action. For the most part though, the best way to use a smartwatch is to let the smartphone drive it – I’d expect most owners to install an application or two (perhaps a fitness related item), but probably no more than this – despite the ‘Android’ bit in the name and the relatively immersive cards experience, we’re still talking a relatively slow and limited accompaniment to your smartphone. Interestingly, there are no buttons on the G Watch – not even for power. Instead, the G Watch is turned on the first time (and also after a factory reset or shut down) by inserting the accessory in its charging cradle – an array of five pins in this provide power and impetus (one presumes that the extra pins can cope with data for some future wired connectivity use?) Magnets guide the rectangular G Watch into the cradle’s hollow and provide some retention, though you do have to get the orientation right, get the G Watch 180 degrees ‘out’ and nothing happens! Battery life under default settings is acceptable – just – at around a day and a half, perhaps two days at a pinch, thanks mainly to the power-hungry screen backlight – how long the battery lasts depends on how much you use the watch, naturally, plus there’s a standby element in that the backlight is also always on to some degree, providing basic time and notifications. Whether this is acceptable life is a personal call – the G Watch is certainly ‘something else to charge’, but on the other hand the cradle is small, accepts standard microUSB input, and it’s the work of only a second or two to pop the watch into the cradle on your nightstand, for example. Android Wear itself is perhaps another weak link, currently – there were plenty of inconsistencies in terms of Google Now integration, partly dependent on how good a network connection my smartphone had, plus I had numerous prompts on the phone asking me to reinstall the Android Wear app for the umpteenth time after doing the same with Google Search. There’s apparently a ‘magic’ sequence in which to do things! These are all just teething troubles, of course, Android Wear is unashamedly still in ‘beta’ and everything will become a lot more reliable in due course.

Verdict

As a day to day companion, for real world use, mid 2014, the popular ‘old school’ Pebble still has the edge in the smartwatch space, with its great outdoor visibility and genuine week’s use on a single charge (I’ll be doing a detailed comparison between this and the G Watch in due course), but the Pebble appears very primitive in terms of software and it’s clear that Android Wear is in a different league in terms of ambition. Give manufacturers another six months to nail screen tech and form factor, give Google the time to polish up the connectivity side of things, and Android Wear should be leading the smartwatch pack. The smartwatch will never replace the smartphone per se, but it’s likely that a really excellent smartwatch may be in most smartphone owner’s future.