Go native for Desktop
Please, for the love of sweet candy, go native on Desktop platforms.
I'm looking for an alternative for Slack as it uses electron which sucks every last bit of RAM it possibly can before destroying your computer in a sweet sweet fire. After seeing the wonderful performance of Office I was really hoping this would be native!
Please, someone with the development experience and financial backing of Microsoft must be able to accomplish this in your sleep. Surely?
Thomas Cove commented
I know this suggestion will be forever buried by important user requests for more cat emojis or whatever but as someone who actually has to manage this conceptually excellent and horrifically implemented app in a windows 10 environment - This would improve everything immensely.
Timothy Carroll commented
This is the best suggestion for Teams, hands down. Most people who submit performance related requests probably don't understand all the nuance about platforms to upvote this, but this needs all the upvotes.
I think it's odd that Teams actually works better in a browser than it does with the Electron based app. There's really something wrong.
Andrew Vijay commented
The time it takes to open a chat window after click is usually 2+ seconds and when system is under load it takes 4 to 5 seconds. Please fix this. Maybe webassembly is the answer for this. All user interactions should be as fast as possible!
Seyyed Soroosh Hosseinalipour commented
I think Microsoft must release UWP version of Teams for resolve all similar problem.
On my Mac, the real memory usage of all 9 Teams processes is 974MBytes (Real Mem) or 1716MB (Mem). While at the same time Microsoft Word only uses 59.7MB (Real Mem). AutoCAD 2020 uses 55,7MB. Adobe Illustrator uses 141,1MB.
Apple Messages, formerly known as iChat only uses 118.1MB. Adium, another (obsolete) native macOS chat client with multiple protocols uses 106.6MB.
We'd really like Teams to be an application, not a browser. If this trend continues with Outlook as well, we will have to reconsider Microsoft products.
Out of all the web engines available, Chrome is the heaviest in resource usage. Webkit uses a fraction of the resources for identical content.
Please understand that Teams needs to run next to 50 web browser tabs, a Mail Client, 2-3 office suite applications, and in most cases at least 2 other chat applications (WhatsApp, Facebook Messenger, iMessage, etc.). And it needs to do that on machines that have 8GB of RAM, that are still sold today. And all without killing the performance and SSDs with swap usage.
I am fine with using electron if the experience is good. You shouldn't pick a technology irrespective of user experience. But the electron-based teams client is very sluggish with UI interactions taking seconds. If the team can improve the abysmal performance without changing technology stacks great! but something should be done.
I concur, it makes no sense for a Microsoft product to use such a bad development framework. MS developed a ton of better ones, but we are left with this nonsense that takes half of my 10th gen i7 just to display a few lines of text.
And don't get me started about the lags...
This is ultra crazy... The choice of Electron where you have to reinvent/recode almost 40 years of GUI research in an ultra non efficient language is beyond me... If we want to save the planet by reducing energy use why use Java Script everywhere?
Be a decent citizen on the OS you run on and use it's optimised framework and follow its GUI guidelines. But I know those are strange concepts to Microsoft...
Yuri Banens commented
It’s not just performance. Native apps can take advantage of platform-specific features such as notifications, inter-app operability, visual consistency in window chrome, keyboard shortcuts and menu items. There’s every reason to make native apps, it’s a false economy to save engineering costs by building it in Electron
Definitely agree - i'm using teams at work, 8 hours per day. It's unusable, especially when you have many chats (when it's a primary messaging app in company you get a lot of). Sometimes the whole window blinks, usually you need to wait at lest a second when you switch the chat, a lot of micro freezes, crashes and it needs too much resources. It's frustrating to use it and we are talking about basic feature - messaging. It's sad that in 2018 we have performance issues with messaging application. First you killed skype, same issues with teams. Slack is also not native but it's not such performance problematic as teams. IMHO current version never should be released to public.
I agree I am having numerous problems with TEAMS. I got a message from Symantec stating Excessive Memory Use and it was TEAMS. Looking at the file it came from I saw Squirrel which is part of Electron. I do not want it on the WEB and I am sure others don't either! You are dragging our systems down.
I cannot echo these thoughts and comments more.
I barely works and is super sluggish and buggy.
Please have the iOS Team re-write the desktop app as it is great on iOS.
Nick R. commented
Using Electron for Teams is insane. I've got an i7 8550 and having Teams, with one chat open, idling means that my CPU is at 20%. It integrates poorly with headsets (I can't pick up or hang up calls with my hardware) and it provides terrible audio quality. All these problems can be *simply* and *quickly* avoided by building a proper client from the ground up with the right team, instead of throwing a bunch of web frontend developers at a very backend problem.
Ember Quill commented
Please go native! Or at least try to improve performance a bit. Teams runs like frozen molasses on our company's VDIs.
Michael Del Corso commented
It's also killing us that teams still uses Electron 1.7.x which is based on Chromium 58.... which is disallowed on our network because it's a huge security risk. PLEASE get this thing upgraded! If Yammer Desktop can use Electron 1.8.x, so can teams!
Emiliano Magliocca commented
totally agree, electron sucks ... that's why I already don't like slack