Performance has been and continues to be a big focus area for Teams. One main area we have made improvements in is responsiveness for the most frequent user actions of switching between Chat, Channel, and Activity. We are also focused on reducing resource consumption and application load time. More improvements are on the way.
Its ok for you to say "we don't care about performance, all we care about is that we can hire interns to write the app"
Then we can at least make plans for how to handle it rather than hoping you somehow decide to overhaul and replace the entire thing..
Its been a couple of years now and this still hasn't improved. Its probably time to consider this electron experiment a failure and move on instead of investing more development time in a solution that isn't working and probably cant be fixed.
I just tried to do a search and like always it locks up the client and I had to kill it from task manager. But then when it relaunched it tried to bring back the application state which in this case was the same search so it would just immediately lock up the client again. I had to kill the client and delete my teams cache files to clear out the client state and get it to launch without hanging.
This is amazingly bad.
I don't think its a memory leak, its just horribly inefficient code. If the search were done correctly it would be server side and there would be no client resources required beyond displaying the search results. So either they've messed that up so amazingly bad or they're doing something even worse like handling the search client side.
Or maybe if you guys don't care about client performance, then create a client API so people can write 3rd party clients that actually work.
Its probably not gonna get better until you ditch node.js.
The delay when switching chats is obnoxious. It reloads the chat every time you switch which sucks when you're going between separate chats frequently.
We are still considering this feature for future releases, and will continue to update the status when it changes.
Pop up banners are extremely annoying even on dual monitor setups. The banner constantly pops on the first screen even when the app is on the second screen. They also aren't useful since most people are constantly chatting and a popup for each message is totally worthless.
Add the ability to move the pop up banner and the ability to disable the banner entirely. Disabling the banner should NOT disable the icon flashing on the start menu. The flashing icon is a much better new message notification and should really be the default with banners requiring manual user activation.
Banner notifications are terrible and get in the way of things constantly. The ability to have the task bar icon flash with sound would be way better.
Hate to be the bearer of bad news. This item has been declined. There will be no work to hide or remove the reply button.
As many people have commented, a big ask is to help improve how people distinguish between giving a reply and starting a new message.
For that the focus will be on this item. “Better visual delineation between `Reply` and `Start a new conversation`”
This is fine. Nobody in my org even uses team chats because they're totally pointless on top of the confusing and terrible UI. We'll just stick to regular chats
Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Also you should be able to punch to zoom on images. Right now pinch to zoom seems to rescale the teams client UI which is bizarre.
This item is still on the backlog.
We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
The problem is a chat is the conversation. To create a new conversation would be to create a new channel for your team. Threaded chat makes absolutely no sense and should be removed from the product.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
My team ends up using a multi party chat instead of a team room because team rooms are under a separate tab and muti party chat is 95% the same as team rooms.
Users are going to spend the majority of their time in the chat tab so the teams tab will be ignored unless they are forced to use a team. Since we aren't forced to use the teams tab, nobody here uses any teams.
So not only should you move team rooms along side chats so that team rooms are indistinguishable from chats, but you should probably eliminate multiparty chats to avoid confusion between these two features which are almost identical.
This is in internal testing. I don’t have exact timing for you, but wanted to let you know it is coming!
Why is this under review? This is the entire reason theres a notifications system in windows 10. If people need to control how, when, and what sends notifications its much nicer to do it from a central system in windows rather than per app. Theres no reason teams should be using its own notifications instead of the native ones, especially with the plans for continuity stuff in upcoming versions of windows.
The current notifications are a pop up window that exists as part of the teams app, rather than being part of windows. this leads to some goofy functionality where the notification shows up in the window list e.g. it is an alt tab target.
There are other weird things too like sometimes it isn't a tap target when using a touch screen.
Even without the wonkiness, the windows 10 notification center was added specifically to unify this kind of thing into one place because its a much better experience.
This item is still under review by the feature team. I have no details as to when a decision might happen.
We know you are patiently waiting for this feature. This feature is being implemented in stages. Fast tenant switching is currently in testing both internally and with early customers. We expect to release to the public in the Fall. I’ll post an update once it’s rolling out.
Full multi-tenant, multi-user support will be added after fast tenant switching.