In December 2012, the first version of Action Launcher released. In this episode, long-time Action Launcher user Jesse Wilson hosts yours truly in a discussion about the ensuing five years.

This is a wide ranging discussion, covering not just Action Launcher itself, but a number of topics including how app development has changed during that time, our evolved feelings device system updates, how to help surface features in an app and much more. But don't be fooled, there's plenty of Action Launcher chat here 😀.

It's the fourth annual "… of the year" extravaganza, in which Jesse Wilson and I each bestow 20 highly coveted and equally made up awards based on 2016's technology news.

Some of the awards include classics like “moonwalk of the year” and “lipstick on a pig of the year”, as well as new entries like “you dropped the ball at the finish line of the year” and special one I felt obliged to add for myself titled “biggest personal egg on face moment of the year”.

Jesse Wilson returns to the show to chat all things Action Launcher with me.

Topics include why there was more than 6 months between Action Launcher updates to start the year and what I learnt going so long between updates. I also discuss my pushing to release the Pixel Launcher inspired update so quickly after the leaks arrived, how the update was received by press and customers alike. Oh, and I both tease a major feature I withheld from a recent update and find a (valid!) excuse to talk about hidden menu items at In-N-Out Burger.

Phil and I break down the Pixel phones, Daydream View, Google WiFi, Google Home and Chromecast 4k announcements. We also discuss whether the event lived up the hype Google set about creating, and chat about what we didn't see.

Hot off the wires, Francisco Franco and I dig into WWDC 2016's watchOS, tvOS, macOS and iOS announcements. What did we like and dislike? What didn't we see that we were hoping for? What did we make of those crazy Music and iMessage announcements?

What's it like to attend Google I/O? Was the venue switch away from San Francisco to an outdoor venue in Mountain View a good move? What quality level were the technical sessions this year? Why do Google keep making seemingly basic mistakes hosting I/O each year? Was the move to abandon the giveaways of previous years a good one?

Many felt I was too negative in the previous episode, where Koush and I broke down Google I/O 2016's keynote. Previous guest of the show Karl Smith was one such person, so he and I decided to dig into some of the areas we disagreed with most in this impromptu follow up episode, and I also offer some further thoughts on what we saw given a few more days to process it.