Brian Gillett-Smith
My feedback
-
3 votesBrian Gillett-Smith
supported this idea
·
-
1,806 votes
We need your feedback! Which button do you like best? Fill out this 3-question survey here: https://aka.ms/ComposeButtonSurvey
Also, we’re coming up against some blocks and our previous ship date of end of year is now going to be early next year. Thank you for your patience. :-)
Please fill out the survey! Tweet me @skprufo if you have any questions.
Suphatra
Brian Gillett-Smith
supported this idea
·
-
7,900 votes
Hi everyone, thank you for your patience since the last update.
We want to extend a huge thanks to all of you who have engaged with us on this topic of compact chat. Your input has been invaluable and helped inform our design and decision-making.
As we look to 2019, we will be pursuing plans to continue to make the product more and more space efficient. We see this as a guiding design principle, as well as a backlog of requests from UserVoice that we catalogue, discuss, debate, brainstorm and problem solve.
This principle is also why we will not be making a sharp design turn towards a permanently heavy dense design. Our user base is a wide range of people — such as high school students, the visually impaired, open source developers, and your every day knowledge worker. Because of our broad reach, we must maintain a standard of…
Brian Gillett-Smith
supported this idea
·
-
67 votesBrian Gillett-Smith
supported this idea
·
-
35 votesBrian Gillett-Smith
commented
This is really odd as other markdown works fine, so why not this? It's very frustrating and a feature that I used all the time in previous chat clients.
Brian Gillett-Smith
supported this idea
·
-
520 votes
This request is still under review.
-Warren
Brian Gillett-Smith
commented
This seems so natural and obvious to me that I actually thought that there was a problem with my configuration when the image links that I shared did not embed! Surely this can't be too hard to implement and would greatly improve the UX of the whole product!?
Brian Gillett-Smith
supported this idea
·
-
289 votes
This is still under review by the feature team.
-Warren
Brian Gillett-Smith
supported this idea
·
-
1,937 votes
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`”
http://microsoftteams.uservoice.com/forums/555103/suggestions/19224826Brian Gillett-Smith
supported this idea
·
Brian Gillett-Smith
commented
I agree that something needs to be done with this. My team have been using Teams for a very short time but have already come to the conclusion that the current system is confusing...
If the idea is to promote threaded conversations, then when a user starts a conversation and hits [enter], the focus should move to that conversations reply input area instead of remaining in the "start a new conversation" one. At least that way a user will not accidentally create multiple conversations when they are actually chatting about the same topic.
If the idea is to be more like Slack and have a main conversation wide side threads if required, then the entire reply area should be minimised to an optional icon. In fact, make is an admin-configurable option - "Users can reply directly to messages" - or something like that?
I would be happy with either solution. Do you know any approximate timescales?
This is a great idea and makes a lot of sense in my mind, at least!