Slow app launch
Right now it simply loads too slowly, and it has that massive in-your-face splash screen while doing it.
Application load time is something we are continuously working to improve, and the team is hard at work on fixes. We have validated a recent regression in application launch time that will be fixed in the coming weeks.
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.
+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!
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)
MS Teams takes over 20 seconds to startup on a high performance developer station.
My developers do NOT work with a chat client that will take so much time for starting.
Slack starts in seconds.
Bye MS Teams!
I gave you my vote. Focus on Teams? I dont see it, this Application is now about a year old. Developers - please cahce something.
(correction - 100Mbps connection)
When Windows boots, Teams opens and then sits there non-responsive for quite a long time showing a person but no detail.
This is on 16GB RAM/1TB SSD/100kbps setup. I.e. a fast environment.
Teams needs to start running and being usable a LOT faster.
Jerry Jackson commented
This really is the absolute worse thing about teams. I HATE THIS. I have contemplated making a screen scraper to make the threads and chats not so painful to browse through. Teams is the only program with chat capability I have ever had this issue with. Even msn messenger in the late 90s didn't have this problem. Mother of god please utilise cache, we don't all have gigabit internet connections like Microsoft seems to assume we do.
Flemming Varmer commented
Unacceptable, and preventing me from deploying to organization.
Fix it now - it is a ten minute hack for any skilled developer team
My goodness, every time you start Teams it's as though it's the first time. Most or all history is gone until it pulls it down from the cloud again. If you want us to use it, make it start in less than 60 seconds.
Dennis Lundtoft Thomsen commented
Agree with the feedback, both load time and splash screen are really annoying to endusers
The splash screen is the worst part, loading would take a while windows is booting. But we do not need to have a splash screen there. It is gonna come a few seconds after