I _used_ to wear a smart watch (all of the first 3 iterations of the Pebble) because I thought it would be useful to know who's calling when I can feel my phone buzzing in my pocket while riding so I can decide whether to pull over and answer it or not. Turns out the answer is alway "no". Either I'm jus commuting and I can choose to call back (or not) when I get to my destination, or I'm on the road and I don't care that I won't get to it for several hours or more.

I'm pretty good at navigating - so I don't want/miss the gps/mapping thing. On trips I'd _much_ rather just turn down roads I've never been on that look like they're headed kinda the right way, and see where I end up. If I need to, I'll check in on the phone when I fuel up every 2-3 hours - but it's pretty rare for me to end up somewhere with no idea of which direction and at least a rough guess of how far away the place I'm headed to is.

I do sometimes listen to music - using in ear headphones that fit under my helmet. I'll _occasionally_ use that for turn-by-turn navigation to if I'm trying to get somewhere in town I've never been before in a place I'm not familiar enough to dead-reckon myself close enough that I can get to a place where I'll get by on remembered landmarks and street names.

> And the last thing I need in my car is phone interface.

Not the target audience for the phone integration features...