Google announced a whole host of new features for Google Assistant on day 1 of I/O ’19. Also on day 1, quietly, and tucked away on the 9th slide of Niomi Makofsky’s presentation; ‘Intro to Google Assistant: Build your first action‘, was the casual statement: “1M+ Actions”.
Google Assistant has 1 million actions
That’s right. Google Assistant has over 1 million actions.
AND it’s only been going for three years.
AND that smashes the number Amazon Alexa skills.
AND Alexa had a two year head start.
Wait, that doesn’t sound right
You’d be right to question how Google has managed to blow the Alexa skill numbers out of the water in such a small period of time. If you’re heavily involved in the voice assistant community, you’ll know how popular Alexa is with developers and how much drive Amazon has behind growing and educating the community.
Although Google Assistant has started to grab its fair share of headline space in the last 12 months, press coverage of Alexa is at worst comparable and, at best, more widespread.
(This is by no means a scientific study, but through looking at my Google Alerts which track articles featuring Alexa and Google Assistant, the number of articles for Alexa typically outweighs the number for Google Assistant.)
Amazon, having constantly engaged in the community, speaking at countless events, hosting and inspiring any number of hackathons, sponsoring and keynoting conferences and developing a decent online presence have managed to grow the Alexa skill base to 143,145 skills as of Jan ’19. That’s across all locals globally.
(That number came from adding together all of the skills in all of the locals from this Voicebot report. So that’s not accounting for the inevitable and potentially substantial duplication you’ll find in all English speaking locals i.e. many US skills are available in the UK and most UK skills are available in the US.)
So 5 years of hard work has gotten Alexa almost 15% the number of actions that Google has gotten in 3 years.
I’m not an Alexa fan boy. I actually think that the announcements Google made at I/O’19 have put Assistant above Alexa in my estimations.
That said, something doesn’t feel quite right about those numbers.
What does Google class as an action?
I think the ultimate confusion stems from what Google classes as an action vs what Amazon classes as a skill.
It’s helpful to look at Alexa skills first for context.
What is an Alexa skill?
For Alexa, a skill is the capability for the voice assistant to do something such as play music, set reminders or book a train ticket. It’s the equivalent of an app on a smart phone. It’s a purpose built, custom made app that runs on Alexa. It could be first party, built by Amazon, such as setting a timer, or third party, built by a developer, such as an interactive story.
What is a Google Assistant action?
Google explain that an action is the ability to extend the capability of Google Assistant. That sounds the same as an Alexa skill. An action is the equivalent of an app, and third party developers can create these apps to add conversational experiences to Google Assistant.
However, if you take a look at the list of available Actions, and scroll through each category, you’ll see that there certainly isn’t 1M+ there.
There’s more to actions than you think
At I/O’19, in the same talk, Niomi Makofsky, Global Product Partnerships, explained the four ways that content creators and developers can craft a presence on Google Assistant.
In the image above, you’ll see that creating bespoke, hand coded from the ground-up actions; the equivalent of an Alexa skill, is just one of four ways that you can create for Google Assistant.
As well as that, you can:
- Add content through using templates; the equivalent of Alexa Blueprints
- Create app actions and slices (the ability to dip into an app to perform a task or dig data out of an app to surface through Assistant)
- Create smart home features, such as lights and lamps as well as custom smart home objects
On top of that, through using schema.org markup on your site, you can have your web content surfaced on Google Assistant.
For web content, Google Assistant currently supports:
And it just announced at I/O’19 support for:
- How to
Now we’re getting somewhere.
Actions are not the same as skills, they’re completely different
Think about that. All of the websites in the world that use schema.org markup are indexed and surfaced on Google Assistant.
Every news site that uses it, every recipe site, every podcast site and, now, every how to and FAQ page across the internet that uses this markup is available for Google Assistant.
And every website that uses it is an action in and of itself
Every time you ask Google to play a podcast, that one podcast is one action.
Every time you ask for a recipe, if that recipe is being served via a website through using schema.org markup, then that individual recipe (or website) is also one individual action.
Every news article (or website) surfaced and, now, every how to and FAQ are all individual actions.
Google has incorporated its search capability into actions
So, from now on, with Google Assistant, you don’t have to build a specific and bespoke conversational experience to have an action. If your website appears correctly in a search result for the above categories, and that search result is what Google Assistant uses, that’s your action.
And then you’ve got Gmail and Google Calendar and YouTube and the other Google-owned products that will all be counted as actions, too.
Google haven’t confirmed this, but how can this not be the case?
Maybe I’m wrong. This is just my interpretation. I haven’t had this confirmed or denied by Google. But its hard to see how Assistant has hit those numbers in that timeframe without this being the case.
And, if that is the case, then Google have not only weaved the web and search into the core Assistant capability, but they’ve also provided plenty of new ways for creators to build for Google Assistant without having to code a bespoke action.
Now that’s smart. Incredibly smart, indeed.