zlacker

>>basemi+(OP)
Please make an unofficial client for windows too. The official one sucks so much it is hard to even describe.

>>hosteu+m6x
I use Teams on Windows extensively at work (for chats, calls, meetings, screen sharing). And I have zero issues with it.

It’s been really solid for me since that major overhaul they did a couple of years back.

Not sure what issues you have, but I wonder if perhaps that us NOT running 3rd party security products is a factor (we only run Windows Defender).

>>jonath+n8x
Screensharing on a browser and trying to change tabs is a constant frustration; you have to wait for that overlay to get into the moveable state. Sometimes I have to switch between chats several times to get it to acknowledge that I've seen that latest message. When you add a code block at the end of your message, it's a toss-up whether you can type outside of it afterwards with the right or down arrow-key. If you can't and you need to, you just have to start over AFAICT. Making the codeblocks in the first place is usually a hassle even though parsing markdown is a solved problem. It has a lot of redundancy with Outlook and I often need to clear notifications from both. Search is unreliable. Sometimes I open an active conversation and it decides to scroll me back a month.

That covers what I'll encounter in a typical week. There are one-offs as well. It's not the worst software I work with, but talking to my team should really be zero friction.