4 ms·
MS Teams has the worst ever "typing status" implementation I've ever seen. In certain cases it shows you're typing by just having the conversation opened, which
by jaimehrubiks 4y ago
MS Teams has the worst ever "typing status" implementation I've ever seen. In certain cases it shows you're typing by just having the conversation opened, which is extremely frustrating. Maybe just because the cursor is in the text box. It should only show typing if I have at least 1 letter...
- gabereiser 4y agoAnd a timeout of at most 3 seconds in case you pause typing.
- radarsat1 4y agoMaybe it's because I use the Linux client, but my experience is that MS Teams is the worst ever implementation of every single facet of chat and video communications. It's really the one popular application out there that seems to have absolutely no redeeming factors, and I'm constantly confused by why it has the uptake it has. I can only conclude that it has more to do with companies preferring Microsoft than because they actually like it, or that it satisfies some policy/legal reasons, (eg. I've heard it's more GDPR compliant.) But purely as software, it's actually the most terrible user experience I've ever had. I really don't get it.
- suprfnk 4y ago> It's really the one popular application out there that seems to have absolutely no redeeming factors, and I'm constantly confused by why it has the uptake it has. I agree about MS Teams being very terrible. I attribute the uptake it has solely to a lot of companies already working with Office 365 (Outlook, Word, Excel, etc) and getting Teams for free -- so why pay for another chat app?
- Jaruzel 4y agoAs we're snarking on MS Teams, let's talk about the fake DnD status, which has been deliberately implementated as a non-functional visual indicator only - it doesn't change the notification behaviour of teams at all, and if you work in culture that totally ignores status indicators, you will get pinged on teams all day even if you have DnD set. Skype for Business had a working DnD, and they chose not to keep the same functionality when MSTeams replaced it.