![]() ![]() Sid: You are capable, and thank you for doing that. They did it-they didn't want to obviously reveal to the world that we were working together, yet, and that's why we asked you politely, Corey, to not see that and be quiet about it. So, what Slack was doing was running an experiment across their entire user base to determine where the regions that are optimal for certain end-users, store that information, perform data analytics on that information, and then apply a meeting hosting algorithm to optimize audio and video latency using our SDK. It's backed by Route 53 and a number of other AWS primitives, which allow our customers to discover regions that are optimal to host meetings. So, what Slack was doing there was an experiment using one of the capabilities of the Amazon Chime SDK to determine what AWS region was closest to the Slack end-user to determine what region to use to host a meeting or to stream video or audio to, and what's the closest region to use to limit latency for customers. You know, there's some limitations in terms of the audio and video capabilities that it supports such as PSTN dialing. They do also have a meetings capability, but it does have some limitations. And they're really good at context management and how to keep context within that particular channel. Its world-class, best team messaging, and collaboration, and a platform for hooking in various different sources into a common channel. In the world of Slack, they've had a focus around messaging. So, it's very easy in our industry to get confused about what is the primary focus of an app? Where are they going? And is Chime supposed to be a Slack competitor? And I'm going to answer Corey that usually these applications have all the functionality that a customer needs to communicate within their enterprise context, but they tend to focus on one area where they're going to do well. They recently introduced a calling ability that actually works with Microsoft Teams. ![]() Even if you look at Slack today, they have a chat capability. And so, it's very easy to be, kind of, misunderstood as to is Chime a chat app? Is it a meetings app? Is it a calling app? What is it doing? And if you look at the world of unified communications today, that's actually pretty common across all of these services. We have a business calling and PSTN connectivity capability. Amazon Chime has a number of different features and different service capabilities. And now you're announcing that you're actually doing business with Slack. We're going to be using Slack, but Chime is there just more or less as a placeholder until an actual competitor comes along. So, Slack has always been the yeah, that's adorable. And that really leaves Slack in that space. I'm not a fan of Teams, because I tried to use it once. Teams was then on the rise significantly, and they tend to talk about all of their daily active users because it likes to open itself, which is, yeah, if you can bundle something in, it works out super well. And then, HipChat, really, discovered that failing to innovate for a decade wasn't the best plan, and Atlassian sold the HipChat stuff over to Slack. You had this, sort of, giant war in the messaging apps, originally of Slack versus HipChat. ![]() But my running joke about Chime for the longest time was that it has no customers because it was easy to fall back on. In all seriousness, don't do that the world has enough jerks in it. If you want to get to know what they're doing, insult their work, and oh, they come at you in a serious way. Join Corey and Sid as they discuss the newly announced Amazon Chime and Slack and partnership and what it means for virtual meetings, where the optimal place to host a video meeting between a user in New York City and a user in Taiwan is, how chat becomes exceptionally difficult when you’re trying to scale to hundreds of thousands of users, how the Amazon Chime team responds to user feedback, how Amazon’s own usage of Chime doubled in recent months and Chime scaled without a hitch, why the Chime team focused on and perfected the app’s plumbing first and how it’s now shifting its attention to polishing the porcelain, why the Chime interface displays a region label, what Sid thinks the number one misunderstanding about Chime is, and more.Ĭorey: So, we started talking when I wound up making fun of your service, which it turns out is a terrific way to meet people. He was also the founder and vice president of R&D at I/O Medical Systems, makers of a device that could acquire multiple physiological indicators using a tablet device. Over the years, Sid’s worn many other hats, including working as a consultant for DaVinci Capital and a program manager at Microsoft. Prior to joining AWS, Sid worked at CTI Group, serving as the company’s CTO for a decade before joining its board of directors. Sid Rao is the GM of Amazon Chime, AWS’ communications platform for voice and video calls. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |