Replace Electron with .NET 6 and Blazor
The dependency on Electron makes using Teams a challenge. I have a very fast dev laptop with a discrete GPU, 32GB RAM, and 10th Gen Intel i9 processors with 16 cores. In the chat window, I clicked a different person's name and it took 6 seconds to transition. Try doing this hundreds of times a day. Sometimes it takes 2 second, sometimes more than 10. But even at its fastest, it's not fast enough. No other app behaves like this and aside from Visual Studio and Terminal, I don't depend on any app as much as Teams. This performance is simply unacceptable. I just read the latest blog post, link below, and it seems there's some really great stuff for making cross-platform native apps. I don't know for sure that the issue Electron, but I've never seen anything perform this poorly that runs natively. I've pasted a section from the .NET 6 Preview blog below and it appears to be a way forward for Teams. This isn't just me, this is everyone complaining about this.
One of the most exciting parts of .NET 6 is mobile development, which is currently offered as the separate Xamarin product. Over time, we’ve been making Xamarin more similar to mainline .NET. It’s now time to deliver a fully unified mobile product for .NET. With .NET 6, iOS, Android, and macOS development will be integrated into the .NET SDK experience and use the .NET libraries. For the past couple years, we’ve been working to fold Mono into .NET, so developers can leverage the strengths of both runtimes without having to target different .NET versions or worry about compatibility issues. In .NET 5, we moved Blazor WebAssembly over, and are using that same model for Xamarin. .NET 6 is the culmination of this unification effort, encompassing a key Epic of the theme – Xamarin developers can upgrade to and use the latest .NET SDKs for their existing apps.
Now that all your .NET apps will run on the same libraries, we want to increase the amount of code you share across desktop and mobile platforms. Xamarin.Forms, Xamarin’s cross-platform UI framework, is evolving into .NET Multi-platform App UI, enabling you to easily write apps for iOS, Android, Windows, and macOS with the same codebase. .NET MAUI is shipping as part of .NET 6 along with a bunch of performance and tooling improvements like .NET/C# Hot Reload, more shared resources and code across different platforms, and better page rendering performance with a more flexible set of UI controls. You can follow the overall Epic: Xamarin/.NET MAUI developers have improved app performance and share more code with .NET 6.
.NET MAUI isn’t just for client app developers. Thanks to the refactored control set and the ability to run on the .NET 6 libraries, your existing Blazor apps will run natively on Windows and macOS via .NET MAUI. You’ll be able to seamlessly weave in native controls and functionality alongside your Blazor codebase, including platform specific functionality. See the Preview 1 blog for some screenshots of “Blazor desktop” in action.
Seyyed Soroosh Hosseinalipour commented
I think this idea is the same with https://microsoftteams.uservoice.com/forums/913786-microsoft-teams-free/suggestions/43512507-please-make-maui-app-for-teams
so please vote them together