Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (56)

On Amazon Prime Video’s move to a monolith May 14, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Stop Shakespearizing Sep 16, 2022 Using GNU Make with JavaScript and Node.js to build AWS Lambda functions Sep 4, 2022 Monolithic repository vs a monolith Aug 23, 2022 Keep your caching simple and inexpensive Jun 12, 2022 Java is no longer relevant May 29, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 In most cases, there is no need for NoSQL Apr 18, 2022 Node.js and Lambda deployment size restrictions Mar 1, 2021 Should we abolish Section 230 ? Feb 1, 2021 TDWI 2019: Architecting Modern Big Data API Ecosystems May 30, 2019 Microsoft acquires Citus Data Jan 26, 2019 Which AWS messaging and queuing service to use? Jan 25, 2019 Using Markov Chain Generator to create Donald Trump's state of union speech Jan 20, 2019 Let’s talk cloud neutrality Sep 17, 2018 A conservative version of Facebook? Aug 30, 2018 TypeScript starts where JavaScript leaves off Aug 2, 2017 Design patterns in TypeScript: Chain of Responsibility Jul 22, 2017 I built an ultimate development environment for iPad Pro. Here is how. Jul 21, 2017 Rather than innovating Walmart bullies their tech vendors to leave AWS Jun 27, 2017 Emails, politics, and common sense Jan 14, 2017 Don't trust your cloud service until you've read the terms Sep 27, 2016 I am addicted to Medium, and I am tempted to move my entire blog to it Sep 9, 2016 What I learned from using Amazon Alexa for a month Sep 7, 2016 Amazon Alexa is eating the retailers alive Jun 22, 2016 In search for the mythical neutrality among top-tier public cloud providers Jun 18, 2016 What can we learn from the last week's salesforce.com outage ? May 15, 2016 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 Managed IT is not the future of the cloud Apr 9, 2016 JavaScript as the language of the cloud Feb 20, 2016 Our civilization has a single point of failure Dec 16, 2015 Operations costs are the Achille's heel of NoSQL Nov 23, 2015 IT departments must transform in the face of the cloud revolution Nov 9, 2015 Setting Up Cross-Region Replication of AWS RDS for PostgreSQL Sep 12, 2015 Top Ten Differences Between ActiveMQ and Amazon SQS Sep 5, 2015 Ten Questions to Consider Before Choosing Cassandra Aug 8, 2015 The Three Myths About JavaScript Simplicity Jul 10, 2015 Big Data is not all about Hadoop May 30, 2015 Smart IT Departments Own Their Business API and Take Ownership of Data Governance May 13, 2015 Guaranteeing Delivery of Messages with AWS SQS May 9, 2015 We Need a Cloud Version of Cassandra May 7, 2015 Building a Supercomputer in AWS: Is it even worth it ? Apr 13, 2015 Ordered Sets and Logs in Cassandra vs SQL Apr 8, 2015 Exploration of the Software Engineering as a Profession Apr 8, 2015 Finding Unused Elastic Load Balancers Mar 24, 2015 Where AWS Elastic BeanStalk Could be Better Mar 3, 2015 Trying to Replace Cassandra with DynamoDB ? Not so fast Feb 2, 2015 Why I am Tempted to Replace Cassandra With DynamoDB Nov 13, 2014 How We Overcomplicated Web Design Oct 8, 2014 Infrastructure in the cloud vs on-premise Aug 25, 2014 Cassandra: a key puzzle piece in a design for failure Aug 18, 2014 Cassandra: Lessons Learned Jun 6, 2014

Amazon Alexa is eating the retailers alive

June 22, 2016

I am far from an early technology adopter. I did not get an iPhone till 2011. A year ago a friend introduced me to Amazon Alexa and I thought it was neat just not for me at the time. I followed the press articles about it nevertheless.

Finally about two weeks ago I bought an Amazon Echo device. Immediately, it became the most used appliance in our household. Within minutes it became clear that Amazon has built something much better and much more powerful than Siri. It also became obvious that Amazon has created a whole new shopping experience that no other retailer has thought of. As a developer I am amazed at the simplicity of building skills for it.

Alexa as a consumer service


This morning I wanted to confirm when my daughter’s piano lesson was. Consider the experience of using your smartphone to check your calendar: unlock, swipe around, find the calendar app, tap on it, realize it is not showing you what you are looking for, swipe around some more, look for a button that switches me to day view, and finally I see what I am looking for.

I didn’t use my phone, however. Having my coffee in the kitchen, I said causally in no particular direction: “Alexa, what’s on the calendar for today?” In a calm voice she replied: “You have two events on your calendar for today. There is Father’s Day barbecue at our house, and there is Miriam’s piano lesson at 12:30.”

Trying to decide whether to have our barbecue outside or not, my wife asked: “Alexa, what’s the weather like today?” and the AI gave us exactly the information it asked. As we were setting up the fire pit outside, I said: “Alexa, please turn all the exterior lights on.” Alexa obediently said “Ok” and activated all five Insteon switches scattered around the house that control our exterior lights.

I am writing this article right now and for some background music I asked Alexa to “play Norah Jones please” which she started streaming from Amazon Prime Music. I didn’t have to swipe anything, didn’t have to tap on anything, didn’t have to press any buttons.

Consider the experience of shopping for household items, like laundry detergent. If you are using your phone, it’s the all too familiar procedure – unlock, swipe, drag, drool, find the app for your retailer, find the product, add to shopping cart, check out, enter your payment information, order. With Alexa, it’s easy: “Alexa, please order some laundry detergent” and she combines your past Amazon order history and product recommendations and offers to order what you need from Amazon.

Alexa is unobtrusive. You don’t know it’s there. It is not asking you to learn any multi-touch gestures. It is not asking you to learn new buttons or a new way of interacting with technology. You are not required to wear anything on your wrist. It serves it’s primary purpose as a connected speaker very well, and it is priced competitively to other connected speakers out there.

Alexa as an application platform


My first computer was Sinclair ZX Spectrum 48. It had 48 Kilobytes of memory. It had built-in BASIC interpreter. The graphics, by today’s standards, was pretty horrible. Despite its limitations it was easy to learn how to program : you turned it on, it booted into BASIC, and you could be on your way towards building a useful tool in minutes.

The very first programs I’ve written were simple text-based tools. They would show a list of choices, wait for the user to input a selection, and then show a next set of choices or perform the selected action. Since 1980s, the computers have become so
complicated that building apps today requires deep knowledge of complex topics. Even users are fed up with the complexity – just consider the examples of finding information using your phone I’ve described above.

It is 2016 now and chat bots are revolutionizing the way we interact with technology. Facebook has invested heavily in the Messenger platform, Amazon is aggressively marketing Alexa-enabled devices, and Google recently announced their Google Home platform. Every major tech company is trying to establish themselves in what is turning out to be the Next Big Thing in how we interact with technology and information.

Amazon made is ridiculously easy to add skills to Alexa resulting in dozens of skills being added daily by individual developers and companies. Because Amazon has the somewhat unfair advantage of having AWS at their disposal, they are able to eliminate all friction that surrounds learning and building software for a new platform.

Since purchasing an Echo, I’ve written a couple of skills for Alexa and submitted them for certification to Amazon. While I used JavaScript to write these programs, I could have used Python or Java with AWS Lambda platform.

If that wasn’t enough, or if I didn’t want to use AWS Lambda, I could have used whatever technology I wanted as long as it could respond to HTTPS requests. Mind you, using AWS Lambda costs me absolutely nothing to host until it starts handling millions of requests – and I should be so lucky to build something so useful that it gets that much traffic. The point is, I was not required to learn any new programming language that I did not already know.

To submit a skill to Amazon Alexa skills “store” I did not need to make any investments. I did not need to pay a dime, or commit to any unreasonable legal restrictions on how I can monetize my skill. I simply used my existing Amazon account to log on to the developer portal and in a few easy steps I submitted my newly written Alexa skills to Amazon for certification. One has already been approved.

As a developer what I like is that Amazon is acknowledging that they do not know what the future holds. They are asking the developer community to help build the platform to its full potential.

Alexa helps Amazon eat traditional retailers alive


Let’s face it. At the end of the day, Alexa does create a delightful shopping experience on Amazon. Consider the shopping experience I described above that used a phone, and compare it with simplicity of saying what it is that you want. Like it or not, no other retailer has thought of this.

Did Walmart think of this ? Nope. Walmart doesn’t even have a developer API and just doesn’t seem to bring their own IT systems up to date. Their Retail Link service only works with Internet Explorer 7 or 8 and looks and behaves like something that may have been built in 2003. Walmart even states as much on their supplier support page.

I don’t normally shop at Walmart. I wanted to try a newly opened one in my town a try. I ordered a couple of lawn chairs for store pick up. The goods were shipped and I got a text message two days later that it was available for pick up. A 15 minute drive to the store, and 30 mins of waiting for someone to acknowledge me at the pick up counter I had my order in my hands. If this was Amazon, it would have been delivered same day to my porch at no addition cost and no time wasted on my behalf. Between Amazon Dash buttons and Alexa, Amazon truly creates a fricitonless shopping experience.

The problem for retailers that compete with Amazon is that now Amazon has placed these devices into people’s homes. Consumers are unlikely to want multiple similar “bots” in their homes. I can see people having multiple voice assistants, but as a consumer I know one thing – I am not going to want more than one connected speaker in my house from different vendors.

Amazon is not preventing any other retailer from creating a skill for Alexa. It would be interesting, for example, to be able to have Alexa ask Walgreens for the status of my prescription. Will traditional retailers swallow their pride and take advantage of Amazon’s technology ? I guess we’ll find out.




Featured image credit: Scott Beale / Laughing Squid