After countless production delays of the Pebble watch, mine finally arrived a week ago. I have been intrigued by the idea of wearable computing devices for quite some time, whether it be watches, glasses, or the human body itself, as seen in research at my alma mater.
As computers continue to evolve and become more pervasive in our every day lives in new ways, I leapt at the chance to back a Kickstarter project that is on the forefront of this movement and that could land on my wrist now. Below are some of my findings so far:
The watch face itself is built surprisingly well for a small indie hardware team. While it is not made of curved glass as a potential Apple “iWatch” is rumored to have, it is comfortable to wear and is lighter than expected. The rubber watchband shipped with the device, however, is bland and mediocre. Fortunately this can be replaced with any standard watchband.
The always-on e-ink screen is very readable in sunlight, and has a backlight that can be activated by clicking one of the buttons or simply a flicking of the wrist (this one took me some time to figure out, but is a welcome gesture). The 144×168 resolution isn’t spectacular, but felt good enough for a secondary screen. My only experience with e-ink displays has been through the first generation Kindle, and I didn’t realize just how much the refresh rates have improved on these displays, as I found the transitions to appear smooth.
The buttons do not feel as sturdy as one would hope, and in fact I have read at least one report of a button falling out. Hopefully I’m not jinxing myself.
To charge the watch a USB-Pebble cable is included, which works similarly to the Apple MagSafe connector in that it latches magnetically onto the side of the device.
This was probably the most frustrating part of the owning the watch so far, as I had to attempt pairing the device to my iPhone over Bluetooth a couple times before getting them to talk to each other. The Pebble iPhone app also crashed on me while trying to upgrade the firmware (yes, there are already firmware upgrades available!).
While I cannot speak to Android as I don’t have an Android phone to test my Pebble with, I suspect that the setup process and overall experience is currently a bit smoother than the iOS one, due to both iOS being more of a closed platform and to the way iOS 6 handles communication with other Bluetooth devices.
The watch is operated with four buttons: up, down, select, and back. It’s a relatively simple interface to learn, and since the app selection is currently very sparse, there’s only so much that can be done on the device. Of course, this will change once Pebble’s free SDK becomes publicly available.
The current features include dismissing notifications as they get pushed from your smartphone, changing watch faces, setting alarms, and controlling music played on your smartphone. The great thing about notifications is that any iOS app that shows up in the Notifications Settings list can be pushed to your watch, which provides a lot of flexibility and minimal setup.
One benefit of having alarms set on the watch is that if you sleep with a partner and wake up at a different time, the vibration motor will only wake you up (and trust me, the watch vibration is more than powerful enough to wake anyone up).
Impact on my life
There have been many benefits to owning the Pebble that I did not anticipate when I initially funded the project last May. The best part about owning this device is that it means fewer times you need to pull your phone out of your pocket.
This is handy in many cases, whether it’s walking outdoors, mounting on my bike while my phone is stowed away under my seat, or even in the shower (yes, the watch is waterproof!). I plan to take it skiing this weekend, which will save me the trouble of having to take off my gloves if my phone vibrates. Another use case is when talking face to face with someone, and not having to pull out your phone, which I find can be quite rude. While staring at your watch isn’t much better, at least it can be done in a more discreet way. In each of these cases, it prevents the user from having to check their phone at every vibration, as a glance at the wrist can determine if the notification is worth tending to.
I only use my phone on vibrate, and there are many times where I’ve missed calls because I simply didn’t feel my phone go off in my pocket, or had my phone somewhere else in the room. I can imagine the same would go for a woman who keeps her phone in a handbag. Wearing the Pebble has already saved me once from missing an important call, as I did not have my phone on me.
As we are currently in the wet season in San Francisco, it prevents me from having my phone exposed to possible water damage if I’m walking outside while it’s raining.
So far with only moderate use of the Pebble, it only seems to last three days at a time before dying on me. It is definitely annoying to have another device to worry about charging all the time, but hopefully Bluetooth 4.0 support and other future enhancements can double the battery life to around a week. In addition, having my iPhone paired with the Pebble watch and having the Bluetooth radio on all the time seems to draw a little more than the reported 10% additional battery drain on my phone. Of course, support for Bluetooth low energy should improve this drain on my phone as well.
The Pebble’s OS has not crashed on me yet, however there are still notifications that don’t seem to make it to the watch unless I repair the devices together and/or fix each individual app’s notification settings. Again, this is more likely due to iOS Bluetooth bugs and there may not be anything Pebble can do at the moment.
Regarding the current apps on the watch, all of the apps besides the music remote control app are passive in that they don’t relay any information back to the phone. Unfortunately, notifications are read-only right now, but it would be great in the future if you could for example choose from a selection of canned messages to respond with to a text.
Another problem with notifications is that you have to dismiss them to get back to the default watch face view (I want to see the current time, this is a watch after all!). Newer notifications immediately replace older ones, and there is no way to currently view older notifications, which becomes annoying if a couple come in at once. In addition, dismissing a notification on the watch does not reflect on the phone, meaning that particular notification will still be need to be additionally dismissed on the phone.
I still find myself having to on and off the notifications setting once in a while on my phone to get notifications pushed to my watch consistently, but hopefully a future firmware update will fix this issue.
Being an early adopter of this technology, my expectations for this device were not set very high. After one week of owning the Pebble, while it does have bug issues to work out, I can say that it has already made a big impact in my day-to-day activities and yet still has a huge amount of potential as more apps are made available. One may think it would get distracting with a device always in view, but I find it has the ability the reduce some of the noise/clutter I deal with on my phone, as I have control over what I want pushed to the watch, and only need to take my phone out of my pocket when I feel the notification is worth tending to. Overall, I am excited to see what the future holds for the Pebble watch and the team, and maybe develop some Pebble apps of my own!