This is under review! If you have more ideas/feedback specifically on this item, please sign up for user testing here: https://1drv.ms/xs/s!AryUNzh1ogZzif8pDcOcx2pW45I87w
You can also tweet me at @skprufo if you have any questions.
Under Review for 4 months. Update?
Quick update that we have made incremental changes and you should start to see those white margins becoming much thinner and chat getting more dense in the coming weeks. It will not be the fully dense mode, but it will be moderate changes so not to jar our full user base. These changes are being implemented across the board, so this is NOT a compact chat mode that is an optional setting, but permanent changes to the UI to increase density.
I’m keeping this item on the “working on it” status because we are going to continue making the product more dense overall. We’ll continue to update you as we make progress.
Big and special thanks to the hundreds of you who participated in the user research. It gave us really great information to make these permanent changes. THANK YOU!
Wow, there was a UI change and it somehow got worse.... Seriously how hard is it to do what people want and copy every other chat app? Discord, Slack, HipChat, RocketChat. They all have basically the same layout and they are the top chat platforms. Instead you guys try to do your own thing and your users hate it and we keep asking for the same thing so you keep doing different things. The people in charge really shouldn't be in charge.
Been a month now since the Twitter Q&A (useless btw, you just have to look at Slack), any update?
We got a flood of feedback in research not to eliminate this button completely, but to minimize it. So you’ll see a design change soon that makes the Reply button a little bit less conspicuous.
Let me know if you have any questions!
Lol at the people freaking out about the removal of an annoying button somehow meaning the removal of an entire feature. You can still have threaded messages (3 dots like Slack) and not have a massive reply button that is bigger than some messages.
Hiya again folks.
I just wanted to write and let you know that I updated the idea to better reflect the vibrant discussion in the community about exactly what a private channel means. It looks like there are five definitions — shout out to user John Black who wrote it out so elegantly. I’ve included that description in the original idea.
We still have this item under review, and I’m personally interested in seeing if this request is further changed when we release guest access (coming super soon!) this summer. Stay tuned, stay cool, and as always, thanks for your support of Teams.
"evaluating ways we can implement this. It’s not an easy fix"
The way to implement it is the way people ask, don't pull a typical Micro$soft and implement something you think people want when they are asking for something very specific.
Also, it is kind of easy to implement. You already did it with teams so duplicate that functionality in channels. If it's not easy, you have spaghetti code.
Lol, "leave Slack and come to Teams because here at Micro$oft we don't implement what you want and do what we want instead."
Send me a tweet at @skprufo if you have any questions on this. I’ll let you know when it goes live.
[insert round of hi-fives to everyone who voted for this]
It’s happening, folks!
Thank YOU for making Teams awesome.
3) does it matter? you have people requesting the feature. As Nike states, just do it.
Code snippets are still in progress. It requires significant work on our compose bar, and thus is taking longer than expected. But don’t worry, ITS COMING. Just longer than spring. I’m super sorry. :(
If you’re interested in testing it, just sign up here:
@Ilya, at 200 lines you should be pasting that in a text file instead of a chat message...
IMO, I would much rather see other features implemented before syntax highlighting. With plain code snippets we can get by, but other things such as compact views, meeting integrations, etc should take precedence. However, this would be a very nice feature.
So it turns out there are some several external dependencies that are hindering our plans for this feature. We are pulling it back into review so we can determine feasibility. Here’s to hoping we find a way to bring this to you — right now its very difficult. We are not taking this off the table though; we know this is an important feature, so we’re tracking the external dependencies to see where they land.
This gained a lot of traction five months ago and seems to have tappered off. Now that we’ve created “Follow a channel” — do you still have a business need for this feature? If so, could you share that information in the thread here on UserVoice, under this item.
Thanks everyone, I’ve sent your feedback over to the Framework team. They are working on a solution. Will let you know as this progresses.
I'm really confused why you keep coming back and asking users why they want features. Here's the deal, Slack does most of the things people keep requesting. It doesn't matter why, just make the features people ask for or else you will not get conversion from a superior application to the inferior Teams. I want to see what users are in a Team/Channel. It's not hard to do.
Start off your weekend with good news: we’re working on this!
Thanks to everyone who brought this feature to the forefront and shared feedback on their use case scenario. Very helpful!
I wrote some more product updates on today’s Teams blog in my weekly column, “Weekend Reading” —