We have been iterating on different designs and are starting to test internally. I don’t have a timeframe but will keep you posted.
I see that the development and product teams are still staffed entirely by Walmart greeters.
I'd like to point out that this is literally the primary use case of Teams. Your product managers are idiots. i'd say your UX people are also idiots, but you clearly don't have any.
June now, I'm guessing the timeframe is "another 2 years."
Microsoft: We have this great idea for threaded conversations in a chat client!
Microsoft: I wonder why nobody has done this before?
Microsoft: Let's just make it, it's genius!
Everyone: ...wtf wait
Microsoft: Why is everyone complaining? Oh well, BLURRY VIDEO BACKGROUNDS!
Everyone: Fix your f***ing chat UI!
Microsoft: *continues playing with *****
-- 2 years pass --
Microsoft: People are still complaining, maybe we should prototype the primary use case of our app?
Is this dumpster fire of a UI getting fixed any time soon?
One assumes that in turning the bottom input into a "New Conversation" button, you could also show the "Reply" input by default for every conversation. You could also do a material style floating action button with a "+" for new convos, if you didn't want to continue your flagrant abuse of vertical space.
One also assumes that you could put an actual designer on this, and prototype with actual people, but since this has clearly never been done I don't know why you'd start now. By all means keep adding features like background video blur instead of spending a day of development time on your primary use case, 1.5+ years later.
It would probably be a good idea to drop some mockups or a preview of the feature or it just makes it look like you're avoiding potential criticism or feedback. Or more accurately, delaying it.
Clippy is flattered by all the attention but plans to continue his retirement.
Clippy was the best part of Teams, and Clippy was never good.
I think the solution to this is just lighting the application on fire and then using something else.
The feature team is still considering this item. No confirmation yet.
All of you people trying to migrate to Teams from actual chat clients should probably try using Teams first before your entire company hates you for it.
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.
This feature is still in the planning stage. No new updates are available at this time.
We’re currently working on defining a compact mode experience. I will post more details when we have more to share.
Currently we have Teams defaulted to show you the first (up to five) channels ever created. If you want to add more channels to your left rail view, just click the ellipses next to the channel name and select “Favorite”. When you favorite the channel, it will then be “pinned” to your left rail under that team name.
Try that and let me know if that meets your needs!
I see this continues to be dumb into 2019.
Currently Teams has a lot of idiotic "defaults." Abusing the favorites function isn't a solution, it's a workaround to a dumb, easily remedied design decision.
This feature is still being reviewed by the feature team. No decision has been made yet. I’ll keep you posted.
This is still being worked upon and making good progress! Stay tuned for additional updates.
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 item is still being reviewed and pending a decision. No new details at this time.
Just the thing for transitioning a company to Teams, a chat client that doesn't notify you about chats. Maybe this is actually a productivity feature?
I can only assume the same idiot who decided we should only see 3 channels at a time is leading the charge on this one too.
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.
This is in internal testing. I don’t have exact timing for you, but wanted to let you know it is coming!