Microsoft Teams 2.0 Will Use Half The Memory

During the #Windows11 event on June 24, we announced that we will integrate Teams Consumer in the operating system. Alongside this announcement, Rish Tandon, CVP, Teams Engineering, posted on Twitter about changes coming to Microsoft Teams Consumer architecture: moving from the Electron platform to Edge Webview 2, switching from Angular to “100%” on React.js for the new version of Teams and leveraging apollo graphql.

With this change, we are taking a major step in #MicrosoftTeams Teams architecture. We are moving away from Electron to Edge Webview2. Teams will continue to remain a hybrid app but now it will be powered by #MicrosoftEdge. Also Angular is gone. We are now 100% on reactjs.

We are also on apollo graphql. And we are going to continue to contribute back to apollo, graphql, reactjs, chromium.

What does it mean?

Bottom line: better and more performance client experience. And following Rishs’ tweet: “Teams 2.0 will consume half the memory of the same consumer account on Teams 1.0”. Why? The Electron framework lets you write cross-platform desktop applications using JavaScript, HTML and CSS. It is based on Node. js and Chromium and is used by the Atom editor and many other apps. Whether you’re running the Teams desktop app or the Teams web app, Chromium detects how much system memory is available and utilizes enough of that memory to optimize the rendering experience. When other apps or services require system memory, Chromium gives up memory to those processes. Chromium tunes Teams memory usage on an ongoing basis in order to optimize Teams performance without impacting anything else currently running. In this way, similar Chromium workloads can utilize varying amounts of memory, depending on the amount of system memory that is available.

The Microsoft Edge WebView2 control allows you to embed web technologies (HTML, CSS, and JavaScript) in your native apps. The WebView2 control uses Microsoft Edge (Chromium) as the rendering engine to display the web content in native apps. With WebView2, you may embed web code in different parts of your native app. Build all of the native app within a single WebView instance. In “Evergreen distribution mode” the WebView2 Runtime is updated automatically so there is no need for the developer to manage it.

Stay tuned!