Other than it being M$ slop, what are the problems with it functionally?
I used to work at a place that has been using Skype group chats (lol) and just a couple weeks before that client left (call center, got moved to working a different company) they switched to Teams for group chat.
Now we only used a team wide group text chat and the supervisors would have separate chats for individual workers.
But the only thing I remember about it was that the emojis weren’t animated like Skype and that the color of the UI looked kinda like the Discord default.
The problem is that they kept on forcing stuff into it till it became a bloated monster.
When teams was the replacement for Skype, it was pretty much just that, a chat and call app.
Now you have chats, calls, teams that are automatically their own SharePoint (not to confuse with the SharePoint sites themselves), contacts, calendar (synct with outlook, but completely different ui and functions), planner (not to confuse with to-do, stuff in the planer can show up in to-do, but not vice versa), power automate integration, power apps integration (that only work half the time cause of missing user rights), OneNote integration (at least that one still has its own app), and a plethora of different apps you can link.
The files in the individual teams take ages to load, the UI changes every few days for the sake of it, basic features break for no apparent reason, calls randomly don’t connect, sound in and output breaks repeatedly.
Its a slow and cluncky mess of different apps tacked onto each other, just so MS can say that they have an app for that instead of forcing you to use the browser interface.
Other than it being M$ slop, what are the problems with it functionally?
I used to work at a place that has been using Skype group chats (lol) and just a couple weeks before that client left (call center, got moved to working a different company) they switched to Teams for group chat.
Now we only used a team wide group text chat and the supervisors would have separate chats for individual workers.
But the only thing I remember about it was that the emojis weren’t animated like Skype and that the color of the UI looked kinda like the Discord default.
The problem is that they kept on forcing stuff into it till it became a bloated monster.
When teams was the replacement for Skype, it was pretty much just that, a chat and call app.
Now you have chats, calls, teams that are automatically their own SharePoint (not to confuse with the SharePoint sites themselves), contacts, calendar (synct with outlook, but completely different ui and functions), planner (not to confuse with to-do, stuff in the planer can show up in to-do, but not vice versa), power automate integration, power apps integration (that only work half the time cause of missing user rights), OneNote integration (at least that one still has its own app), and a plethora of different apps you can link.
The files in the individual teams take ages to load, the UI changes every few days for the sake of it, basic features break for no apparent reason, calls randomly don’t connect, sound in and output breaks repeatedly.
Its a slow and cluncky mess of different apps tacked onto each other, just so MS can say that they have an app for that instead of forcing you to use the browser interface.
I have no idea what one note it share point are, but that sounds hellish.
They are now animated