To ensure a seamless transition for our customers and to continue delivering new value during the development of the new architecture, the following strategic approach was implemented. Key decisions made included participating and standardizing on the Fluent UI collection of UX controls, transitioning from Angular to React for building user interfaces, moving data processing out of the main thread to a client data layer worker, and lastly, transitioning from Electron to leverage WebView2 as the host. Recognizing this, the team began analyzing available technologies, benchmarking, building prototypes, and defining the new architecture known internally as the "north star". However, as the capabilities and innovation of Teams expanded significantly over time, it placed strain on device resources. When the development of Teams began in 2015, these choices enabled the rapid delivery of cross-platform web and desktop clients. The classic client of Microsoft Teams used open-source software such as Electron as the host, AngularJS as the web development framework, and a variety of custom controls constructed using HTML and CSS. The consumer version of Microsoft Teams has already begun using this new architecture, and the preview version of the upgrade for commercial customers will initially be available for Windows, with support for web, Mac, EDU (education), and VDI (virtual desktop infrastructure) to follow later in the year. This post shares insights into the goals and expected benefits of the modularization and layering that have been implemented. Microsoft Teams has made a significant investment in the re-architecture of its desktop client, with a focus on providing a simpler user experience.
0 Comments
Leave a Reply. |