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
From a UI perspective, Teams is terrible, but there is one thing it does well and that's large meeting calls. Microsoft knows their customers: large companies.

The boss doesn't see that you can't properly paste a piece of code in the chat, but he wants to make sure that everyone hears him at the annual talk. He wants it to connect to the company directory, make analytics, reflect the corporate hierarchy, make announcements, etc... He sees it as a one way, top down communication tool more than peer-to-peer, and for the former, Teams delivers. Developers hate it, but developers are not the ones who have the money and make these decisions.

Still, that's a thing I miss about Bill Gates's Microsoft. It was certainly evil (Embrace Extend Extinguish, the fight against free software, etc...), but at least, they actually cared about usability and developers, not just pleasing big company bosses.

>>GuB-42+TQx
Completely agreed. I sit in dismay, remembering the Microsoft I frowned upon back in the days as a Linux/FreeBSD user. But at least their software was accessible via keyboard and their translations were really good.

Fast forward to now, after being a dev on Windows for years and loving it, and now their UX is a joke. For example, to jump back and forth between chats, neither the back/forth mouse buttons nor any other key combo works on macOS. You have to click the navigation buttons in the symbol bar instead. Translations are AI-powered, and that shows. Also, Teams is dog slow, which I also count as a UX issue.

>>v1ne+WRx
It’s sad to see the decline in the quality of desktop computing. I blame this on the rise of mobile apps and Web apps in the 2010s. It’s not that mobile apps and Web apps are inherently bad; that’s not the problem. The problems is that we have an entire generation of engineers who never learned desktop UI/UX conventions and principles.

To make matters worse, in an attempt to save on development costs, mobile and Web applications have been deployed on the desktop, with the justification that it’s better to have an app, even a shoddy one, than to not have one at all. What’s appropriate on a smartphone or a tablet may not be appropriate on a desktop, and vice versa. The Web never had a mechanism for enforcing UI/UX guidelines, similar to the MS-DOS and Apple II days of computing.

The sad thing is Microsoft and even Apple now have shoddy desktop apps, despite the fact they have the resources to make well-designed desktop apps, and that at one point they set standards for excellent desktop apps and conformed to them.

We had a sweet spot in the 2000s with Windows 2000/XP/7 and Mac OS X and their ecosystems of desktop applications. It’s been downhill since.

>>lingua+eay
Even Microsoft MacOS apps are second-class citizens next to the ones found on Windows. I personally feel this is $WORKING_AS_INTENDED because honestly why would Microsoft empower people to exit the platform? It would be like creating an open source version of Active Directory and giving it away.