The document compares Amazon Alexa and Google Home in terms of integration technologies, user interaction, and development features. It highlights the differences in activation processes, invocation naming, state management, conversation design, and versioning between the two platforms. The future trend suggests that voice interaction, powered by AI, is becoming vital for customer experience, with Google Assistant rapidly advancing to compete with the more established Alexa.

1. AMAZON ALEXA VS GOOGLE HOME BOT
MOBILE FIRST TO AI FIRST
Over 15+ years of industry experience in
integration technologies, API, SOA and
Cryptography. Exposed high end cryptographic
encryption technologies using following Quantum
Principles using Quantum Computing. Currently
working one of best Non Profit Health Care
Company in USA Blue Shield of California and
proud to be part of BSC. #WeNeverStop
Connect Me at:
https://www.linkedin.com/in/tarunchawdhury/
tarunchawdhury@gmail.com
I CODING

2. AI BOT Reference Architecture
User
BOT
Cloud AI
Engine
Cloud API
On-Premise API
REST API
REST API
Speech
(voice)
Speech
Over
Internet
(bytes)
Dummy Device
with lots of Micro
Phone and
Speaker
This is heart of whole ecosystem. It does three
key activity:
1. Speech to Text and Text to Speech
Translation aka NLP – Natural Language
Processing
2. Provides Machine Learning based
Supervised Learning Platform which
enables user provide their own customized
Data Set to train the model to fulfil a
custom action
3. API Integration
Supervised Learning
Training Data Set

3. Google Home Vs Amazon Alexa
Google Home Amazon Alexa
Discovery
Google Assistant does not require any activation. Once published it will be
available right away to the user
Alexa user needs to find and activate the BOT using Alexa mobile app after publishing.
Alexa wont recognize the BOT until its activated explicitly through app
Invocation
Google provides flexibility to developers to customize the invocation name. e.g.
“May I talk to my Blockchain Teacher” or “Could you connect me to the Blockchain
teacher” where “Blockchain Teacher” is the name of the BOT
Alexa uses a predefined invocation for its BOT. e.g. “Start my Blockchain Teacher” or “Ask
my Blockchain Teacher” or “Run my Blockchain Teacher” where “Blockchain Teacher” is the
name of the BOT and “Start/Run/Ask” are the predefined phrase which Alexa understands
Intents
Captured the functionality requested by the user and any additional data
required to fulfill the functionality through custom Entities
Captured the functionality requested by the user and any additional data required to fulfill
the functionality through Slots. Alexa provides many built-in slots like movies, tv shows, names
of people etc. This makes it more reliable than custom slots defined by developers.
Manage State Google uses Contexts Alexa uses Sessions
API Endpoint Supports Multiple API Endpoint per BOT Single API Endpoint per BOT
Account Linking
Supports OAuth 2 and implicit code flows for authorization. As there is not explicit
activation required login must happen during user interaction from the server
Supports OAuth 2 and implicit code flows for authorization. Alexa user must login when
activating BOT from app or when server responds back saying login required.
Conversation Design UI Interactive UI called API.AI to create Conversation and provide training Data Set Interactive UI called Alexa Skill to create Conversation and provide training Data Set
Review and Publishing
Manual Process where reviewer actually use the BOT and send feedback
following a strict guidelines on security, branding, privacy and terms of service.
Developer needs to provide instruction and sample data to test the BOT.
Generally provides feedback within two days of submission
Manual Process where reviewer actually use the BOT and send feedback following a strict
guidelines on security, branding, privacy and terms of service. Developer needs to provide
instruction and sample data to test the BOT. Generally provides feedback within two days of
submission
Versioning
Google Assistant provides versioning where multiple version of the BOT can be
active simultaneously
Alexa as of now does not support any versioning.

4. Future Trend
As a part of omni channel revolution voice has become
one of fastest growing digital channel for user interaction
and customer experience ( Thanks to AI – Artificial
Intelligence’s Machine Learning capability)
Both Alexa and Google’s platform provides intuitive way
enable voice as key channel and become an integral part
for customer experience.
Alexa has been in the market for quite a while now and
has become more matured and adapted platform now.
However Google appears to have prioritized Google
Assistant and catching up fast.
One of biggest advantage Google has over Alexa is
Google Assistant is available on any Android device.