zlacker

>>basemi+(OP)
The official client is absolutely terrible. But, I've found a much better solution: I tell all my customers Microsoft Teams doesn't work for us and they'll have to pick something else.

Kudos for at least trying to address this, MS should hang their head in shame, this is not the hardest problem to solve these days. If we could do it in 1995 they should be able to do it 30 years later.

>>jacque+G6x
I use Teams every day (for work, the company basically runs on it) for chat and meetings, and I'm one of those strange people who never really have much problem with it. I can think of one occasion in perhaps the last six months when it crashed and I had to kill and restart it. Otherwise it just sits there on my laptop and does its thing. Same with Outlook etc.

So, what am I doing wrong? How do I get the authentic Teams user experience that everyone else here seemingly has?

>>andyjo+Rkx
The biggest problems with Teams -- which I had to use daily for over a year and a half at my previous job -- is with its UX, not its implementation. I found bugs in the Linux client here and there, but they weren't showstoppers. But using it was just frustrating because it got in the way of communication and didn't work how I expected.

It's just not good. When you compare it to Slack, etc. it's just constantly awkward and getting in the way. And it tries to do too much, on top of that.

Slack is rapidly getting shittier though, so.