I want to like Gboard. On paper it looks really rather good. It's a keyboard from Google, it ties in with your account, it syncs things, it has clever searching for emoji and gifs and the like... what's not to like?

Problem is, I've been a user of SwiftKey since around 2011 (I think it was). I'm very used to how SwiftKey works and it also contains a lot of handy things. I like that it has smart completion, that it learns how I type a bit skewed and that it takes this into account, that I can turn off the fancy swipe typing and instead make use of handy gestures like swipe-left to delete a word. I like some of the themes a lot.

Into the mix comes my iPad, which I use on occasion. The standard Apple keyboard is horrible and, sadly, I find SwiftKey on iOS just as frustrating. It seems to lack enough key features there (especially the word deletion gesture, as far as I can tell) that it's also a bit annoying. My dream of a consistent typing experience across all devices just wasn't happening -- until I found Gboard on iOS.

That felt almost right. And from what I could tell it worked almost exactly the same on iOS and Android. So it felt like a good time to try and force myself to use Gboard on my Google Pixel and Nexus 7.

Sadly, though, I'm just not getting on with it. It's okay. It's not bad. It's just... not good. I'm finding that it lacks enough useful things that it's a frustrating experience. Little things like: when I enter Google Search, there's no word completion in the keyboard (SwiftKey has that); the word deletion gesture (swipe left from the backspace key) seems very hit-and-miss; the most obvious completion for a word sometimes appears in the middle slot but, other times, in the left slot. And so on.

Nothing huge. Nothing that's a show-stopper. But a handful of a little things that make me miss the comfortable home that is SwiftKey.

Don't get me wrong, it does have some very handy and cleaver features too. The searching for emoji -- including showing them up as word completions -- is rather clever. The gif-search thing is all kinds of fun too (mostly used to annoy the hell out of my son on twitter).

None of those quite make up for the bits I miss from SwiftKey though.

All that said, I've being making a point of pushing on with Gboard, thinking that most of my issues might just be because I'm too used to my "old home". Mostly this was working well, until I noticed something this morning. While reading the description for Gboard I noticed this handy thing in the "Pro Tips" section:

Sync your learned words across devices to improve suggestions (enable in Gboard Settings→ Dictionary → Sync learned words).

Useful! I'd assumed that this was the case anyway -- it's Google after all -- but it's good to know I can ensure it's turned on. So I went to turn it on. This is what I found:

What the hell Google? Sure, I do have a Gsuite account on my phone -- as in various apps have access to a Gsuite account (Gmail, Drive, etc...) -- but it's not the primary account on my phone and it's not the account I'd really want to be doing the dictionary sync with anyway. If I've got dictionary sync I want it tied to the keyboard no matter the app I'm in, and no matter the account I'm using in that app. I want the keyboard to be tied to a specific account when it comes to sync (just like SwiftKey does it).

This, I think, is a show-stopper for me.

I can overlook the other niggles, I can learn to cope with it not being quite so perfect in some situations; but the blanket inability to do something as simple as cloud-sync the predictions and learn from how I type -- things that are, these days, central to what Google's about -- it's frankly stupid.

I guess I'm going to have to keep Gboard as a backup keyboard for those times when I need to find the perfect gif.

For the past two years I've, mostly, being happily using a Google Nexus 6 as my phone. In the past six months or so I've started to notice that it hasn't been quite as good as it was. The main problem, for me, was that the camera was starting to play out. The issues were the ones that I've seen reported elsewhere: use of the camera would quickly make the phone laggy, very slow response times on pressing the shutter, occasional failure to save an image, etc. This was generally frustrating and, even more so, because I'd got back into photoblogging.

Meanwhile... I've been lusting over the Google Pixel ever since it was originally shown off. I was some way off my phone contract renewal and the price of a new Pixel was something I just couldn't justify. Last week though an offer cropped up that meant I could renew early and get a Pixel (including a free Daydream headset thrown in).

Fast forward to Monday just gone and...

So far I'm liking it rather a lot. It is odd that it's smaller in my hand than the Nexus 6 was (the XL wasn't an available option and I was also starting to think it was time to drop down in size a little again) but I'm also finding it a little easier to work with; it's also nice that it fits in trouser pockets as well as jacket pockets.

It feels very fast (although every Android phone and tablet I've ever had have felt fast to start with) and smooth to use. I especially like the default feedback vibration -- it's a lot smoother yet also more reassuring than any I've felt before.

The Google Assistant is proving to be very handy. I'm sort of used to it anyway thanks to having owned an Android Wear watch for a couple of years but having it on the phone like this seems like a natural next step.

Another thing I'm getting very used to very quickly, and really liking a lot, is fingerprint recognition. I didn't think I needed it but now I'm wondering how I ever managed without it. Combined with the notification pull-down gesture that the recognition area supports it seems like a perfect way to open the get going with a phone.

There's a couple of niggles with it, of course. The main one for me is the lack of wireless charging. That was something I really liked about the Nexus 6: I could be sat at my desk and have the phone sat on top of a charging pad, staying topped up. No such handy setup with the Pixel. The other thing is the lack of water resistance. To be fair: it's not something I've ever really felt I needed with other phones and I'm not in the habit of sticking them under water; but knowing that it doesn't matter too much if it gets exposed to rain would be nice.

Other than that... there's not much else to say right now. It works and works well, the move from the N6 to it was pretty smooth and the Pixel has fallen perfectly into my normal routine.

Now and again Google seem to actually listen. While they do generally have a bad habit of removing things from things and saying it's for everyone's good (because options are bad and they can't maintain them, apparently) it seems they can do the odd turnaround now and again.

One thing they removed from Android recently was the "until next alarm"" option when putting a device in "do not disturb" mode.

Seems they've added that back in 6.0.1:

It's a small thing, but it makes so much more sense and makes things so much easier (even if it's a trivial thing).

Nice one Google. More of this please.

I actually can't remember when the change was now, it was either Android 5.0 or one of the 5.x point releases, but I can recall the frustration of Google having changed how you make an Android device silent, or not. The idea seemed clever enough but it was a real pain to switch to and use. Previously there'd simply been this neat system of setting he volume to either be some non-off value, vibrate or totally silent. I even had a neat little widget on the home screen of my phone to allow me to toggle between these 3 states.

It was simple, and worked well.

The new system though.... ugh. It was confusing and so much more long-winded to work with.

At some point though they added one big redeeming feature: "Until next alarm". When I got into bed I could tell my tablet to go totally silent until my alarm went off in the morning, and then it would all work as normal. That was an utterly brilliant idea.

So it made sense that if they changed anything about this in Marshmallow they'd keep that in and make it even more awesome, right? Right?!?

Well fuck!

Why? Just..... why?!? I actually prefer how the new one works. They've more or less solved the problem of how it was more faff to deal with, they've solved the problem of having to cock about with the volume rocker to get at the settings and then set the settings. I like all that.

But taking "Until next alarm" away? That's just nuts.

Sometimes I really get the impression that the Android developers are like the Chrome OS developers: they're having a ton of fun improving and onward developing the system but they have little connection to how people actually use this stuff.

It's been quite a while since I used voiced search on my Nexus 6. Ever since I got the Moto 360 I've not really had a need to say "OK Google" to my phone because I could simply say it to my wrist. Today though, because I wanted to quickly look something up and my phone was to hand, I spoke to it and got this:

Brilliant.

I've been here before. I had exactly this sort of problem with my Xperia Z at one point. The problem appeared to go away eventually (actually, it sort of came and went a few times over a matter of weeks, if I recall correctly), although I never really got to the bottom of the cause.

I've tried rebooting the phone and that hasn't helped at all. While it's more of a vague annoyance than anything else (like I say above, my Android Wear device is my goto tool for talking to Google these days) it does frustrate a little when fairly expensive tools don't "just work".

Following on from yesterday's problem with the Android Wear timer I think I now have a solution. It came up while chatting with Mike McLoughlin about the issue.

I got to thinking that this problem felt like one that I've seen a number of times before with Google stuff. One thing that's rather common (in many cases for very obvious reasons -- you can't cover the whole world in one go) with Google is how they struggle to get languages and localisation right. This felt like it was a similar issue. Mike had reported that his watch appeared to be unaffected by the issue (I'm guessing he's on the latest version of Wear -- the conversation headed off in a different direction before that became necessary) so I checked what his language was on his phone. Turns out he was the same as me: British English.

So much for that idea.

But then he suggested switching to US English and back again.

Happy enough to apply a very Microsoft "turn it off and on again" approach to a Google device (really, all big tech companies really are the same and really do suffer the same issues) I switched to en-US on the phone and tried setting a timer in voice on the watch.

It worked!

So then I switched back to en-GB on the phone and...

...it still worked!

I've tried setting timers in voice on the watch a few times since and it's yet to fail.

It would appear, as odd as it is, that this is the fix. Well, a fix.

I didn't pay too much attention to it when it happened but it looks like Android Wear, on the phone side, got an update in the last 24 hours. Only this evening did I notice that this seems to have broken something I heavily use on my watch: timers.

I find the timer facility on Wear especially useful when I'm cooking, either to ensure that different parts of the cooking process come together at a sensible time, or when I put something on and need to go off and do something else (perhaps come back to the office while and get on with some work as something bakes, etc).

To be clear, the timer app is still there and, if I select to start a timer "by hand" on the watch, it works as it always has done. Also, if I say "OK Google, set a timer for five minutes" it still does the voice recognition thing:

It's what happens next that's the problem. Before it would have started a countdown timer. As well as vibrating the watch when the timer runs down the timer app also has the very useful feature of showing the countdown on the watch face. This means you can glance every so often and see how long is left to go.

Instead, as of today (well, this evening when I made dinner was when I first noticed it), it starts an on-watch alarm app instead! This is utterly useless. Sure, it does still vibrate the watch when the alarm time arrives, and the alarm time is the right offset from when the timer was requested, but it lacks the on-face countdown.

It's an alarm.

It's not a timer!

Looking in the Wear app it would appear that the correct application is assigned to the correct action:

As such, I'm at a loss on how to fix this. I can't find anything on the watch itself that could be done to change this, and I've tried restarting the watch on the off chance that something went a bit odd.

It turns out too that I'm not alone. I found a thread on reddit where others have the same problem.

What really bugs me about this is that this is very Google. I've run into this sort of thing so many times before, be it on Android, ChromeOS or in their apps in general. They'll change (or screw up) something that's very simple and straightforward and in common use, something that should show up in testing pretty easily. Surely there has to be some way of pushing out an update without screwing up the apps that are assigned to actions?

As much as I really like what Google offer, as much as I value their services and global platform over the other choices, this sort of thing frustrates the hell out of me.

I woke up this morning to find that one of my more recent favourite websites, Medium, had finally released an Android application. I'm more of an avid reader than a writer on there (I've only ever written 2 articles on there, and have toyed with the import facility too) so I imagine the app won't make too much of a difference to me, but it was nice to see that something that had been iOS-only was now on Android too.

I installed it on my Nexus 7 and Nexus 6 and then, given that I have an iOS device now, I installed it on that too. In doing so I noticed a very curious difference:

vs:

Notice how Android has Google as an option whereas that's not an option on iOS? The curious thing is, when I installed it on my Android devices, I logged in with my Google account and it all just worked. I was into my account, there were the sorts of stories I'd be interested in, and there were the couple of stories I'd written.

On iOS I logged in with my Twitter account and the same thing happened (I don't use and don't have an account on Facebook).

It was than that I had to think about how I even logged into Medium normally (via the web, which is what I'd always used up until now). Seems I'd always used the Twitter login (which would make sense).

So here's the thing that's got me wondering now: when I logged in with my Google account, how did it make the connection to my Twitter account? I mean, sure, there's got to be enough data kicking around to actually make the connection and it seems like a safe enough one to make but... huh? I must be missing something here though, it's as unexpected as it is handy.

It's also worth noting that if you go to log in to the website Google accounts are not an option (there is a sub-option for "Android Users" where you have to create an account based off your email address, from what I can see).

I'm left trying to decide if I missed a step here, if this is clever, or if this is just plain creepy (and who's responsible for having made the connection).

Edit to add: Cara from Medium was kind enough to notice my tweet pointing to this post and let me know the how and why of the above. Turns out it's what Rich suggested in the comments.

Yesterday evening I finally got the following notification on my Moto360:

Given the charge was quite a way below that I took the watch off and put it on charge and then did the update later.

From what I could tell it all went pretty smooth. After updating it even offered me a little tutorial on some of the new things it's added. So far I've used (or set up) the following:

• The much better "launcher" Finding and running apps on the watch was always a bit of a pain, so much so that others had even written special launchers for Android Wear. This seems to be pretty much solved now. Pressing and holding the watch's side button will pop up application list, from here you can swipe right to your contacts (them letting you send messages, start calls, etc) and right again for the usual list of actions that you used to go straight into.

The way it's done now makes a lot more sense and seems far cleaner.

• WiFi I've yet to notice the benefit of this, but I've not paid too much attention yet either. The watch now does WiFi. This is supposed to mean that it can still work with my phone when it's out of Bluetooth range. I say I don't know if it's working yet because I use an app to tell me if my phone is out of range and it still keeps tripping as normal -- but I'm unsure if that means it's simply telling me it's out of BT range but really the watch is now doing its thing over WiFi, or perhaps the phone connection really has been lost despite me having set up the WiFi connection. More testing needs to happen here.

Setting this up was curious: I had to turn it on on the watch and then select the access points I wanted to work with, again on the watch. But to actually connect I had to switch back to my phone to enter the AP passwords (which makes perfect sense of course, nobody wants to type passwords into a watch face).

• Gestures These needed to be turned on in settings. I've being using them this morning to navigate cards on the watch and it's really well done and really natural. Simply put, you flick your wrist up, or down, to "flick" from one card to another. All it seems to be missing is some method of gesturing that I want to swipe a card out of the way.

Other than the above it's pretty much business as usual. Hopefully there's been some work to improve battery life and all that sort of stuff, and only time will tell if a difference has been made there.