I really like Teams. I do. But the current chat layout is not suited for professional chats. It's way to space consuming. It looks like something imported from MSN with smiley's that take half of the screen. I would say that Slack have nailed it because they focused on the ability keeping a tight window with lots of chat text visible. In Teams the window is full and starts scrolling after like 10 sentences.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
Mike Ely commented
Move on this ASAP. For crying out loud, Redmond, how slow can you go?
Yes to this.
Dennis Baskin commented
Making threads a second class citizen or making threads an option only would be ideal. Threads are better managed in slack.
The ability to adjust the size of the text input window would be a great addition here
Joe Clarke commented
Need a 4K portrait mode monitor just to read conversations.
Hans Erik Jensen commented
Slack will serve as an excellent guide for pretty much what everyone here is upvoting.
Yes, please make the Teams chat take up less space (need a compact mode)! Currently I have to make the window very large to show my contacts AND the chat.
Rob Nicholson commented
>Uservoice is becoming more and more meaningless over time - MS please put some urgency behind this
Hmm, I know what you mean. Biggest problem, aside from Microsoft taking way to long to implement to features, is the fragmentation of individual posts. I recently had an idea/wish and when I searched it, I found that at least 30 other people had the same idea, worded slightly differently, but spread across separate ideas each with 10 or so likes. If they had been merged together, they would have had more clout. So somebody (Microsoft) needs to actively merge duplicates together.
As for this particular idea, I'm okay with the current implementation. It goes reasonable compact: https://i.imgur.com/li6tAgE.png - and the mobile version is very compact. Maybe just do the mobile view on PC as an option?
Uservoice is becoming more and more meaningless over time - MS please put some urgency behind this
THREE YEARS LATER
Uservoice is really helping status update with these critical needs
J Johnson commented
Why has this still not happened? Our company has just switched to Teams from S4B and it's so imposing on the screen I end up closing it. I also don't want to have the latest chat open at all times in order to quickly see if a contact is online.
@Emmanuel Preveraud: Thank you for posting that. Very helpful indeed.
Overall Teams is not a competitor to Slack or another IRC style app. It is really a replacement for Google Groups.
Slack organized around communication channels not people or groups of people. Integrations connect to channels and conversations not teams of people. Until teams makes visible all of the channels and people regardless of the Teams they are members of, it will continue to be quite different from Slack. I cannot effectively conduct multiple chat conversations at once in Teams because I cannot see conversations without selecting the Team first. So currently I default to group chat and direct chat and lose much of the integration capability of Teams.
Deal breaker missing features so far:
No self messaging
Can't pin a message so it is persistently visible while chatting
Can't pin files so they are persistently visible while chatting
No checklists in a channel
no / (or escape character) integrations (have to move to an app)
No real organized help files or access inline from chat (e.g. /help convert to team, /help message self) Should also autocomplete after finding the syntax.
No editable Status if you have a bounce notification on your email. (huge to optimize comms flow)
Emmanuel Preveraud commented
Periodic repost of the CSS workaround https://userstyles.org/users/727497
What does Planned mean? Typically a plan involves a schedule. So.. whats the schedule?
Nearly 3 years later, still waiting. It's embarassing showing Teams to my company and asking them to get behind it when it's so... 2010. Why is it so hard to fix this with 134,000 employees? It's... not even being worked on, just Planned. It's #3 on most requested feature and you're not even working on it?
I'm guessing the GUI is so hardcoded to a certain width and spacing that they have to do a total rewrite of the GUI code to accomplish this goal (dynamic width). The only updates they came out with were minimal spacing changes, ie, changing a number. But even a small team can do this update in 2 years! What's the hold up!?!?!
Alex, can we please get an update on this request? It's been awhile.