I mean aside from technology choices, It's just very bad at video calls.
I don't want an "artistic" layout of people that is constantly switching around, or comedy "sitting in a theatre" options. If someone doesn't have video on it'll confusingly highlight some random other participant while they are talking, and when nobody is talking it'll choose a random person with the microphone on and boost whatever background noise (or typing) it can up until it matches speaking volume.
Despite randomly boosting silence, it'll aggressively gate anyone talking, with an obvious fade-up at the start of their sentence and if you are lucky, aggressively cut off the end of their sentence. If you aren't so lucky, it'll do this in every pause between words.
Add to that, random disconnects, chat randomly not working, finding it hard to actually get a list of participants, and that it apparently wants to be slack but makes it hard for people to work out how to actually re-use a channel for the next meeting.
But of course it gets bundled in with all the other office stuff the company purchases; making it the "default" that you have to fight against using. We were only saved against moving to Teams for _all_ our telephony by the fact that it's linux support is really, really bad and that's what all our engineers use.
- It's basically a Skype reskin, so it has a lot of visual elements and quirks that carry over from that — most of them haven't aged well. The reacts alone are taken straight from Skype, and they never seem to sync up if people react to a comment in quick succession. It seems like a small complaint, but it's really surprising to see in something built by a trillion-dollar company.
- Speaking of UI issues, why does Teams insist on using a custom notification bubble instead of using the native ones that all other electron apps seem to be able to do? They don't play well with full-screen apps, and they're generally pretty clunky.
- Video calls also fall apart if you have more than 4 people in them (even if most people aren't sharing video). This has led to screenshare drop outs for seemingly no reason.
- I don't understand why Microsoft thinks Teams needs to do _everything_ productivity related; it's a mediocre video chat client, a _really_ mediocre text chat client, and possibly the worst calendar I've ever had to work with, which is saying something, because most other calendars I've had to use are pretty awful. The scheduling assistant alone is one of the most counter-intuitive pieces of UI I've ever used, and managing event ownership is a nightmare. IT had to be called in to delete a zombie event that was supplanted by a new event, but the owner of the original event had left the company.
Not to put too fine a point on it: I've had to use a lot of chat clients over the years, from IRC, to Slack, to Jabber, plus some less professional-oriented software like Discord and Steam chat (which is itself pretty bad), and I can say honestly that my loathing for Teams burns with the passion of a thousand suns. That anyone would deliberately choose to pay for it baffles me.
Try doing a video call with 4 computers. Rather than the oh-so-obvious 1/4 of a screen each, one person gets half, two people get quarters, and you're in a tiny square in the bottom corner.
Even more comical is when one of the participants in using a laptop with two people in front of the camera. Teams will often centre the image, clip the sides, chop off both people, and show the other participants just the empty space between them.
How on earth did this pass QA, or any kind of design review?
My university pays for Google Meet too, and has a server running Moodle, so I have no idea why professors prefer Teams over Meet+Moodle. And don't get me started on Google Classroom...
The downside is that it is clunky. But even then, it’s exponentially better than native SharePoint, WebEx, etc.
Over time, I’m sure they’ll do what they did with “OneDrive for Business” and build services over time to replace or augment that underlying stuff. OneDrive was a turd a 6–8 years ago but got much better about 2 years ago and seems to get incrementally better.
I think part of this is the fucked up way that Teams handles storing content, because it uses a mishmash of SharePoint sometimes for real file attachments, and some ephemeral blob storage for pasted images.
But it's infuriating because there is no error message, or any way to force reload; you just have to keep trying and hope it works, or go into your AppData folder, nuke the cache, and restart Teams.
It really doesn't make sense to me how such a simple common functionality would break in such a major product. Do they not use Teams... at Microsoft? Did they not notice?
Teams v2 won't use Electron[1]; but for now you can get a small performance boost by just opening Teams using a modern web browser (Edge, Chrome, Firefox) at https://teams.microsoft.com/ -- you can even set up a PWA-type app shortcut.
You can uninstall the client after that. I think there's maybe one feature (popout chat windows) that the client has which you can't get in the browser.
I'm a Firefox (beta) user myself, but I would rather try another browser before blaming a webapp -- many issues.
- I need to use the main menu to enter as a named external user in one tenant, to join and bypass the waiting gate to enter the call. Despite my main account being the same email, and indeed SSO!
- While in that call, you receive notifications from chat messages in your main tenant chat inbox.
- You can't use chat in your main tenant, as you're currently logged into a call as an external in another tenant (still using your main account), so you can see notifications for your messages, but can't reply to them on that device (!)
This is before you consider the use-case of having multiple actual 365 accounts (which Microsoft seems to amazingly have failed to deliver on, despite the fact supporting it would likely increase their bottom line, by making it easier to add contractors into a tenant more easily). Strangely, this is supported far better on mobile, but not at all on PC (!)
It seems they've built it on such a complex architecture of accounts, external users, guests, tenants etc, that they need to unwind this complexity to make it work - which tenants' policies should apply when on a call as an external user, but chatting in another tenant simultaneously?
You’ll get a notification from a Teams instance in one tenant, but you need to switch accounts entirely in order to take action on it, which is REALLY slow for stupid reasons.
Also, you can’t run multiple instances of Teams signed into multiple tenants to work around this, and video conferencing is broken in all sorts of ways if you use Teams from the browser
Slack is organic free flowing conversation, like a chat, that you can thread out of for expansion of a particular though via threading.
Teams is forced threading on each thought and then constrained followup with no ability to thread because you're already in the thread.
I can deal with the tech limitations it's the fundamental UX that makes it a huge garbage pile that is being forced on people because "we already pay for it and all our employees are in it. Also hard to build custom bots for if your organization limits admins.
The text in the left sidebar almost looks distorted.
It’s weird.
Often messages just... don't load. To be precise: in a channel you have posts with replies below them; the default view shows the last two replies if there are more. So far so good. Then I click on the button to show more of them, and zero, one, or two more show up -- of the tens that are there. If I reload the page (back to 2 replies) then click the button again, it works as intended, including loading even more if there are many replies.
Then I switch to a different channel and back to here, and it's broken again. Have to reload and retry.
This happens for many but not all reply threads (haven't figured out that pattern yet). However, either a thread always works or it always works only after a reload. Fully deterministic.
This same issue happens with emoji reactions on posts (sometimes only appear after a reload), and the three-dots more-options button in the hover panel of posts: the three-dots button will just be blank white and not do anything until a reload. There is a slot for the button though. It's funny until you have to deal with it (can't edit!).
This is infuriating since it means that when I'm monitoring some channels as TA for a course, I have to constantly reload the page -- which in turn means that I need at least one browser teams open. This is because:
- In firefox, I cannot video call, only voice call. (Why does every other conferencing software work in firefox but not teams?)
- In chrome, I can video call, but while I screenshare my own camera gets disabled -- deterministically. This is something I see with everyone (their camera turning off when they share their screen), so it's not just a quirk of my setup somehow.
- In electron desktop teams (linux), I can do everything, but I cannot reload because it's not a browser! So I cannot fix the brokenness caused by the not loading of content that I described above.
I've reproduced the content not loading issue on another person's Windows pc in native teams, so it's not a linux quirk -- but even so, it also happens in the browser for me which shouldn't be platform-dependent.
My coworkers have joked that maybe MS is designing for this because people having two instances running at all times, frequently reloading one of them, increases engagement metrics significantly.
Does anyone else have this or is my account just broken?
EDIT: I wanted to report to MS but it's impossible to make a screen recording that doesn't reveal personal information of roughly everyone. And MS says that a recording should not contain personal information.
That with Kopete and KDE3.
MS could write a multiplatform QT5 client perfectly by using 1/10 of the resources.
What makes it bad: First of all, it uses Electron, thus it is laggy and wastes too much resources. Maybe it is just a pet peeve of mine, but I hate, if an application does not look native on my GNOME Desktop and does not follow any HIG.
Another factor is the proprietary nature of MS Teams. If it was open, there would probably be some other client/some way to have a real native client.
My preferred alternative would either be Jitsi or Matrix, although both have just electron clients they atleast attempt to have a usable GUI. (Except this one thing in Element: The search button is next to the "Start Videocall"-Button)
I can't replace it, as my university uses it.