Google I/O app

We're headed to Google I/O this week in San Francisco. It'll be my fifth, which is a little hard to believe, and it's more than a little humbling. I still feel a little out of place around all the engineers and developers — the insanely smart people who make this dream job of mine possible. A lot of it's over my head, but at the same time I continue to learn a great deal about how the pieces of Android all come together. There are times I wish I did that sort of thing for a living, or even as a hobby. (I get the same feeling when I listen in on our internal tech team.) Code's just not my thing, though.

I say that as a reminder to myself of why we're at Google I/O this week. It's all about the building blocks for what's to come. It's easy to look at the announcements and pronouncements and then sneer and snicker when the more lofty of ideas doesn't come to fruition right away. (Android at Home, anyone?) But that doesn't mean they're not being worked on. And that doesn't mean we won't see something rise from a pile of ashes in the future. (Android TV, folks?) And above all, Google I/O is less about (or should be less, IMHO) about the shiny end products and more about making the sausage.

But you don't have to be much of a seer to be able to say this: There's going to be a lot of cool stuff this week. Google's official I/O page lives here, and you'll be able to watch a lot of the sessions live. You can stay up to date with all of our coverage here, and of course we'll be liveblogging the keynote on Wednesday.

Stay with us, folks. This is going to be fun. Thanks, Google, for doing it.

A few more thoughts on the week that was ...

  • I'm writing this before Sunday's World Cup game between the U.S. and Portugal, and I'm very much looking forward to this one. A lot of high spots in the tournament so far. But I still can't come to grips with all the diving. It's bad for the sport, and extremely bad for all the kids watching the games.
  • Back when I played, I'd give someone a reason to stay down if they pulled that shit.
  • I'm a mellow old man now, though.
  • So good to have a new "Through Glass" column, especially one from Myriam. But I agree — we've got to get that template working better on more than just desktops. (But I disagree in that it's unreadable on mobile. It's just not ideal.)
  • I can neither confirm nor deny this one. But those who are regular listeners of our podcast may recognize a few hints.
  • A week ago I mentioned on Google+ that I thought we could have done that OnePlus One at OppoMart story a little better. (And I still think we could have.) But as a follow-up to those who were screaming "scam!", I'll mention this: They honored the request to cancel my order without hesitation. Can't ask for anything more than that.
  • Not exactly a shining moment for our newsroom initiative. That post never should have happened, and the mistakes that led to its publication were readily apparent to me as an editor, and for that you have my apologies. We'll do better.
  • But you know what? That's also part of growing as a publication. Hiccups and mistakes will happen. Even bad ones. You work in this business long enough at a high enough level and you'll suffer more than a few.
  • That doesn't make it sting any less, though.
  • A mid-shower revelation on Friday, a couple thousand words later, and we've finally got our picks for the best Android smartphones as of the mid-point of 2014. I don't think any of the choices will surprise you, though the order we've put them in might. Some folks will agree. Some will disagree. But I think we got it right. Look for this on Monday.

That's it for this week. Time to enjoy some soccer. See ya'll on Monday.