Office 365 tenants are now getting to use Loop components in Teams chat. Some are very excited at the new technology; others are less so. It all depends on how you use current composition tools and how easily work habits can embrace ever-changing Loops. In this article, we look at some of the challenges facing user acceptance of dynamic composition as seen in Loops.
Teams is the first major Microsoft 365 application to ship support for Fluid components. Teams chats can include components like a task list, checklist, table, or paragraph. When a live component is sent to other chat participants, everyone involved in the chat can edit and update the component. It's a new way of collaborative working which challenges traditional approaches. Fluid components will also find their way into applications like OneNote, Outlook, and Whiteboard. Looks like a good thing, but how do these components work in practice?