As a result, we didn’t have to create any new accounts to incorporate Chime into the project. However, we have all been using the AWS infrastructure for a long time, even for various aspects of the system at hand. After all, Amazon made its public API available just 6 months before the start of the project.
The truth is that neither I nor any of my team members were very experienced with Chime. The Amazon Chime communications service wasn’t the only solution we considered, but it eventually emerged as a clear favorite. Now, why is Amazon Chime the best tool to implement this functionality?
There were also some essential requirements expressed by the business: As such, it’s not possible to associate a user with an existing account based on ticket data.
User accounts are single-use and removed after an event because the ticket does not have any information about user accounts. The exception is the history of messages, which is to be archived. Most unused resources, such as users and channels assigned to an event, are to be deleted as soon as possible. Chat resource creation needs to be monitored to ensure that throttling limits set by Amazon Chime are met.Instead, we should create a separate service that handles it. Due to throttling issues ( read our API throttling case study of the same project to learn more), resource creation should not be directly connected to ticket data retrieval.All chat resources should be created prior to the event.
#Amazon chime sdk js registration#
There is no need for registration because the account is created automatically beforehand, following the purchase of a ticket. The chat becomes accessible immediately after the user types in the ticket code.For starters, all participants of chat-enabled events should be able to access the chat feature.The chat app had a couple of technical quirks compared to a typical app of this kind due to the way it relied on actual physical tickets sold for a particular event: In order to understand this, let’s go over the technical and business requirements of the chat. What was the problem with that? Requirements That’s why going forward, I will focus on that pesky text chat.
The first three elements did not pose any particular challenges. A text chat for the artist and fans to interact.An emoji functionality designed as an easy way for fans to express their emotions during the live event.A WebSocket-based security feature that makes sure that only one device is logged in for each ticket code.A ticket gateway that includes a form the client fills in by typing their ticket code.The landing page itself includes a number of features: Once filled in, the system would generate an event landing page for the fans to enter. It consisted of a number of easy-to-complete forms. The functionality responsible for setting up a new event is most relevant for organizers. The platform was designed to make it as easy as possible to stream an event for both organizers and fans. Challenge – to build a chat app for an event streaming platform
0 kommentar(er)
