Gartner Blog Network


Amazon’s IoT Dash Button – Worlds Are Colliding!

by David Yockelson  |  May 18, 2016  |  Submit a Comment

Last week, Amazon announced the availability of a “generic” Dash button. If you’re not familiar with Dash, then either (1) you aren’t reading my blogs enough (incredible!), (2) you don’t shop with or read about Amazon (no way!) or (3) you’ve been too busy spending time away from your computer or smart phone to do either one of those. Just in case, here’s a quick refresher: just north of 100 Dash buttons have been created by Amazon to enable instant replenishment of key items such as Gatorade, sunflowers, diapers, condoms, detergent, etc. They work seamlessly with your WiFi, and once you’ve taken the two minutes to set up your button, you can order your item(s) instantly. Heretofore, the Dash buttons have been preordained – that is, labeled with a supplier’s logo and “wired” to a specific product – when ordered from Amazon (at the cost of $4.99 each that is credited to your first purchase through the button).

Last week, this changed. Amazon released a non-labeled and not preassigned Dash button that links to capabilities – that is, services – on Amazon Web Services (AWS). Gentlemen, we have cross over! This may be the first example (other than the existence of AWS itself, which grew out of excess capacity related to the Amazon infrastructure) of a cross over from Amazon e-commerce or retail to AWS! But why am I and others so excited about this (the new button was sold out almost immediately despite its $20 price tag)? Basically, Amazon has provided a $20 “art of the possible” environment for developers by linking the IoT Dash button to its new Lambda services as well as other capabilities resident in AWS. Oh, yeah – you have to have an AWS account to program the button — of COURSE you do! But once you do, you can create any sort of integration or logic tying button presses to AWS’ IoT and other services. Of course, given that a command can only be a button press, the range of actions are somewhat limited – counting clicks, initiating a process, stopping a process, etc. But since the back end node.js, Python, Java, Lambda, etc facilities are available, a button click can initiate a pretty wide range of services.

Amazon has basically made available $20 PoCs (proofs-of-concept) to anyone that wants them while exposing unlimited numbers of potentially new users to AWS. Not only is this good for Amazon in terms of increased exposure and new IoT/Dash button applications, it’s good for organizations that want to try out IoT services without making huge commitments. Of course, there’s a “commitment” made to AWS and back end services that might be added beyond those that relate to button activities (data storage, transactions, etc.), but after all, Amazon is a “for profit” company.

A few weeks ago, I gave a presentation to a client that happened to be in financial services, and I asked why, somewhat jokingly, that company could not have a Dash button of its own to enable its customers to hypothetically execute a trade? Turns out I might not have really been joking, and similar examples might not be hypothetical after all.

Category: digital-business  iot  non-tech-to-tech-providers  

David Yockelson
Research VP
1 years at Gartner
30 years IT Industry

David Yockelson is a Research Vice President on the Tech Go-to-Market and Sales Strategies team in the Technology and Service Provider Research organization.. Read Full Bio




Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.