> Does teams have bugs?

Yes.

I mean, everything has bugs, but it's significantly worse than slack. Here's a short list of my weekly irritations:

- shared images sometimes give you a placeholder empty box while loading.

- shared images sometimes never load from their shared placeholder boxes.

- when auto updates happen, they sometimes result in teams just being broken and has to be explicitly killed before it can restart

- the `code` format tags don't work in chats, only in 'teams' (maybe this is a feature, who knows?)

- sometimes the UI doesn't load and you just get a white empty page instead of a UI, despite being 'online' and receiving notifications.

Not everything, all the time, but consistently noticeably buggy.

I have not experienced any of these bugs. My shared images always load, my automatic updates always work, my code format tags work in chat, the autoupdate is so invisible that I've never noticed it, and the UI always loads.

One thing you listed I do have, but I don't consider it a bug:

> - shared images sometimes give you a placeholder empty box while loading.

That's to let you know that it's loading, and to expect an image to appear.

I use teams on MacOS (intel), Windows, and Android.

Are you on some weird or old beta version?

I discover new bug every week, and my colleagues are also treating it as "working as expected" when they find only a few bugs. You are extremely lucky to completely avoid bugs in Teams.

I think your experience is unique in this regard. Teams is well known to be extremely buggy on MacOS - I've experienced everything the OP has.

Are you currently experiencing those issues?

What's your version of MacOS and Teams?

I've experienced so many Teams bugs over the past few years that it became a running joke. Didn't keep a list though, but by far the buggiest piece of software I had to use on a daily basis.

Also just... a horrible piece of software? Dealing with multiple organisations was such a pain. When I was using it I never got notifications from the other organisations except by email sometimes many hours later. I'm not sure if it's a missing feature or a bug. Whatever - same effect.

It also liked sometimes randomly and continously consuming bandwidth - I'm not sure if that bug ever got resolved or what it was actually doing.

I've never had to use teams over multiple organisations, but I do remember that it did not support multi-account until much further down the road.

I think if I had to use teams on multiple accounts simultaneously, I would have loaded the web app in separate firefox multi-account containers. (I do that at home to keep all of my work and home accounts separate and it works like a dream. It's probably the one feature you can show to get people to switch away from chrome when you show it to them.)

I'm unaware of the bandwidth usage on MacOS & Windows since I've always just used the building's connection. Teams on my Android phone hasn't seemed to cause any bandwidth issues though.

messages just don't send and you only find out hours later, even though later messages are sent

you just stop getting new messages, think you have a quiet day, until you restart teams and see a flood of missed things

does audio work? let everyone try to disconnect/reconnect to give out whose problem it is

Those message issues sound more like intermittent network issues to me.

The only audio issues I've ever seen with teams are actually user issues where they install teams on a new computer, get into a call, then don't read the big popup box that says "teams needs permission to access your mic, follow these steps".

Granted, both MacOS' System Preferences app and Window's Settings app make this more clunky then it needs to be, but that's an OS issue, not a teams issue. (Hopefully it's easier with the upcoming MacOS Ventura's redesigned System Settings app, but based on the screencaps I am not holding my breath.)