Slow app launch
Right now it simply loads too slowly, and it has that massive in-your-face splash screen while doing it.

29 comments
-
Anonymous commented
The loading screen that can't be minimised is a pain.
-
Anonymous commented
This is true - when you close the app it takes few seconds to launch again. However, if you open it from the minimized system tray then it will launch instantly.
-
Anonymous commented
Michael Rebbec is spot on. Everything is slow.
-
Michael Rebbec commented
Not just loading, but every button click in Teams takes far too long.
-
Graham Downs commented
+1 for proper caching. Coming from a Slack background to Teams is just painful.
-
Anonymous commented
It feels even slower when you recognize all the grueling effort that got it to this point.
-
CG commented
When...oh when...oh when...will the performance issues with Teams be sorted? In particular Shifts...abominable...and the rest of the app when you're in a video call...btw Zoom doesn;t seem to suffer from this
-
Antônio A. R. Costa commented
I don't understand why Microsoft has yet to solve this problem. It is very unpleasant!
-
Clovis Lasta commented
Incredibly slow, too much! Msoft must do better
-
Anonymous commented
Entries are made to a collaborative spreadsheet in excel and then saved. Once the sheet has been closed, the updates do not show. I have tried refreshing connection, I have tried switching tabs, and I have deleted then reinstalled the file. Latency is between 5 and 10 min. The file size is 162KB. Not a big file.
-
Anonymous commented
This is just an ridiculous app - I do not see myself waiting for any app that long.
-
Manos commented
I am facing the same issue. It is not easy to work with multiple organizations if it takes forever to start teams and even longer to switch organizations.
-
Alexion CRM software commented
+1 for proper caching, ajustable by users
-
Anonymous commented
+1
-
Anonymous commented
Please implement caching. This request was made two years ago. Adding caching to an app does not take that long and every user would benefit.
-
Anonymous commented
+1 please implement something to address this
-
Michael Vlach commented
It takes forever to start in comparison to everything else. Not to mention the insulting messages in the start up square like "Almost done. We are getting you connected.". What on Earth takes this long? And why do you have to deadlock the main (UI) thread with it???
-
Bart Read commented
I notice this particularly because I have to restart Teams a lot due to its poor handling of network changes/intermittent disconnection.
Here's a scenario:
- I need to quickly post a message to someone on Teams
- Teams won't post it because it's disconnected and won't reconnect
- I quit Teams
- I restart Teams, and then I wait for a minute or two before I can post a message (not an exaggeration)Like most people on here, I'M BUSY, so I don't have the time for all this messing around. Teams needs to be faster, more reliable, and of generally higher quality than it is at present. Comms is a key part of what I do so being forced to used something slow and fragile for this is a real hit on productivity and focus, and a daily frustration. Please sort it out!
-
Anonymous commented
This is Electron under the hood, or? "Station" does a good job of caching/data persistence and has something to say about it on Medium (Station is an implementation in Electron).
With Teams, it does a great job of bringing work together, but that work being reloaded when jumping between tabs slows everything down and "defeats the object" of trying to be more productive.
Currently I'm pinning my hope on Station supporting Teams (currently stuck on an older unsupported underlying Chrome engine)
-
John Shield commented
I suggest users should be able to set the amount of time to download, similar to setting autoarchive on Outlook folders (e.g. archive everything older than 6 months, cache everything newer)