This suggestion is still planned. I don’t have further updates on timing, but will share as we have them. Thanks.
Good news! My group of Microsoft developers (and the rest of the company) is moving to Slack today! My company bought Office365 Premium that includes Teams -- which makes it "free" to use. But, even the "free" version of Teams costs too much. As a longtime Microsoft developer, this is a sad day. But, definitely a very good day now that we will have a tool for professional communication.
Teams UI is clearly a problem. But, I am much more concerned about a company -- Microsoft -- that antagonizes developers while publicly stating:
1. "Empowering developers"
2. "Microsoft has been a developer-focused company..."
3. "First, we will empower developers at every stage of the development lifecycle..."
Just a few samples from public statements. And, yet this thread -- primarily developers -- is pointedly ignored. The highest voted UI request ignored.
As reminder, developers and the managers who once were developers make software decisions. Antagonizing recommenders and decision makers is usually considered a negative in sales and marketing.
Teams UI is embarassing. To pointedly ignore your core constituency ... priceless.
Of course, that is just my opinion. I could be wrong.
"still in the works".
Not sure how to take that. I am pretty sure that the Teams team does not understand "compact".
1. Hiding or moving the Reply button has been declined. The Reply button is a major contributor to unused space. Moving or hiding the Reply button is a major step toward a compact layout
2. Teams auto hides comments!!!!! Actual comments. Actual information is auto hidden. But, all the wasted white space remains. Wow. Talk about not getting the message about "compact". For 10,000 years of human communication, humans have iteratively compressed the white space in order to have denser information because denser equals easier and faster. That is why we use alphabets and not heiroglyphics. Compress the white space NOT the information!
For the record: "compact" means more information, less wasted space.
Clearly, Microsoft if NOT reading this thread.
A few weeks ago, on an investor website called SeekingAlpha, the subject of MSFT (Microsoft stock symbol) came up. Developers supposedly are key to Microsoft's strategy. And, then a couple of the comments below the article brought up Teams as a "brand damaging" application. Brand damaging. Interesting choice of words.
Flash forward a couple of weeks and Microsoft announces the the purchase of github with the words "empowering developers" in its announcement. And, then there is Teams -- widely hated by developers as evidenced by the 598 comments and 4,583 votes for a "Professional" layout.
An interesting conflict of priorities at Microsoft. It will be interesting to see how it turns out.
The comment below had a great deal of right justification ... removed. Ironic.
Based on the 585 comments so far ...
Teams is not suitable for professional programmers.
and distracting lines
The right justification is crazy.
violates all of the
rules for communication.
is very, very low. And
noise is very, very high.
It is apparently
difficult to communicate
this concept to those who
handle the requirements
Make this comments
section use the
same layout as Teams.
And, see if you find it
as I do.
And, could you please
give us the ability to copy
& paste code?
I am glad that Microsoft has
many who like this type
of layout. But, it appears
from the comments
that professional programmers are not
in that group of happy campers.
Teams (as best as I can tell) emulates Facebook and Pinterest: big bold around names, avatars that get their very own column, lots of distracting colors, white space as well as boxes that absorb space and add noise. All of this noise makes it very difficult to read or use for communication between professionals. Emphasis on "use for communication".
If the goal of Teams is professional communication, then please remove ALL of the distracting elements -- or provide a means to do so.
As noted by others, the signal strength of Teams is very low and the noise level is high. To be useful, the signal to noise ratio must be dramatically improved.
As a developer specializing in and with many certifications for the Microsoft stack, I had much higher expectations for Teams.
I downloaded and installed the latest Teams version this morning (3/28). Could not tell a difference although it is possible it compressed slightly.
Please remove (or provide a setting that removes) all whitespace -- emphasis on "all". As part of that white space removal, please move the Reply button up to the Name line. Reply is effectively white space because it adds no information. Currently there is white space between every message -- a single pixel line is sufficient for a separator. White space makes the information less dense which slows reading. And white space is an effective full stop that further slows reading. I believe that removing whitespace was the intent of the original request of "create a professional compact chat layout"
The team is still working on this fix, as part of a larger design change. Given internal feedback, it has been decided the current design isn’t ready for primetime.
In the meantime, someone discovered that triple clicking will actually select all of the text. I know we want the real fix, but thought I’d share.
Thanks for your patience.
I have found the key to when copy works and when it does not.
IF the user name appears in the tetxt block, THEN the "... [bookmark][thumbsup]" appear in the line above the text. CONSEQUENTLY the text can be copied.
IF the sender adds a second line AND the second line does not include the sender's name, THEN the "... [bookmark][thumbsup]" appears in the same line as the text, CONSEQUENTLY the text is covered by the "...[bookmark][thumbsup]] and the text cannot be copied.
I rarely use the [bookmark][thumbsup] features. I could easily get along without those features. I constantly use the copy/paste feature. Copy/paste is a fundamental requirement.
Suggestion: remove the [bookmark][thumbsup] or put them somewhere that they cannot do harm.
Very common. Impossible to select text from a single line comment. A typical use of a chat by a programmer is to forward a database primary key, a member ID or a ticket number -- i.e. a very short identifier. These identifiers typically cannot be selected and, therefore, cannot be copied and pasted. There are exceptions, but I have not figured out the pattern that causes the exception. Reproduced by our ops team that manages Teams.
I have learned to start EVERY message with ">". Adding the right arrow (or greater than) as the first character changes the chat box to block text where anything goes. And, whatever is typed or pasted can always be copied and pasted by the recipient. The right arrow is also a work around because Teams does not have code pasting that I can find.
Feature request is still being worked upon.
This feature request is still being reviewed. The team is working hard to make numerous changes with regards to notifications, but they haven’t forgotten about this item.
I hope to have more details soon.
Missing notifications is so common where I work that most of the time, IF a developer bothers to send a message using Teams, they walk over and let you know.
Chat traffic has dropped significantly since we moved to Teams for reasons such as this one. Its just easier to use another communication method.
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`”
The feature is still being worked upon. Many different changes are going into Teams and will provide a slow but steady pace to our performance increases.
I don’t have any new details at the moment but hope to get some additional feedback in the next several weeks.
Agreed. For my money, remove the Reply button completely -- or provide a setting to do so. It wastes space AND it causes a great deal of confusion. Once a Reply thread is started, then it jumps ahead in the sequence such that other replies -- that did not use the Reply button -- are lost. At the very least, provide a setting -- per room -- to remove Reply. A simple hide works.
When we first got Teams, this was a problem. Now that people have actually used Teams, it is no longer a problem because most people stopped using chat. And, one of those reasons was this exact problem: it is very difficult to switch between conversations.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
I have to agree: Teams is NOT about professional communication. It seems to be an attempt to have Facebook in the office. VERY difficult to use for communication in a professional environment. But, it comes with O365 and managers think that it is "free". Teams is a huge impediment to communication because the goal appears to be a Facebook for the office app. We were using an Atlassian product that is targeted at comm Since being forced to Teams because it is "free", participation has steadily dropped. Developers are not big fans of Facebook at the office it appears.
6 votes1 comment · Public » Accessibility (keyboard navigation, reader, colors etc.) · Flag idea as inappropriate… · Admin →