At the very least their web version needs to have parity with the desktop application. It's 2019, browsers can handle voice chat and screensharing!
Remember this next time their PR team tries to pull another round of "Microsoft has totally changed you guys, we swear! The new Microsoft loves Linux"
Edit: probably https://snapcraft.io/teams-for-linux
Not really. They are making more money than ever. They don't have customers asking for a Linux client in large enough numbers. That's all it is.
By leveraging browser technology they have a platform that is incredibly extensible. Building that from scratch across iOS, Android, Windows and macOS is not feasible. And the benefit of having people reach to the tools at hand and strengthen Office's position outweighs the performance penalty.
Building a few chat apps is not feasible for one of the largest software companies in the world ?
Almost no other platform can guarantee that a UI elements will look pretty much exactly the same on all different operating systems.
Most people don't mind the extra RAM consumption for some applications... as long as the app works!
Apps are lauded for providing "dark mode" now; when ten years ago I simply switched GTK themes.
To say nothing of accessibility.
We've gone way backwards in UX.
Even "simple" stuff like Tcl/Tk is not trivial to get working easily or well.
HTML + CSS + something like React is miles simpler than writing something for Gtk. Qt has QML now but the C++ Qt bindings are _pretty hard_! And after all that work you don't (by default) get an app that resizes as nicely as the HTML/CSS box model does!
I think that WxWidgets has one of the better usability stories for cross-platform native, though.
If someone wrote a good feeling UI library that generated native UIs and had good JS and Python bindings, so many people would be happy to use it, I think. But right now, despite all the shortcomings, web tech is pretty easy to prototype in.
In a perfect world, every application would have minimal dependencies required by the OS, and completely encapsulate their runtime and UI components, making them very portable... which is basically web apps, hence Electron's popularity...
And different systems have different UI requirements, so I don't think it makes sense in many cases to have the same UI between them. iOS and Android, for example, have very different standards surrounding what buttons mean, and how the navigation should work. The back button on Android, for example, completely removes the need to a back button in the application, while in iOS it is still required. And of course if you are making an application that runs on both touch screen devices, and devices with keyboards, the UI should definitely not be the same.
At least the web platform is open enough to do this and still function.
Except for working pretty well on most apps
>However, if you change things like stylesheets and icons, you should be aware that you’re in unsupported territory. Any issues you encounter should be reported to the theme developer, not the app developer.
Themes are rarely problematic and it would take 10 seconds to check if one supposed it to be problematic.
They could perhaps work on solving actual problems.
Or you can just accept that whenever you let someone configure the UI in an advanced way, it is possible for them to make the UI more confusing. Just because it is possible for someone to mess up your app with a bad config, doesn't mean it is best to remove any kind of configuration at all.
But, the trade off is simply unpredictability. The app is assuming that the OS has all the components it needs, at the correct version etc. Not all OS's have all components you think, which leads to unreliable user interfaces, which may work for small applications with only a few OS dependencies, but as the app grows the reliability decreases...
You're correct in saying the UI should not be the same on every platform (iOS, Android, Windows). But in my opinion the app should encapsulate it's UI and share as little as possible with the host OS.
If a component is not available, it means it's not appropriate for that platform or not part of the UX guidelines.
Your "perfect" world isn't. It leads to a fragmented landscape of competing runtimes and UIs, is inefficient and results in extra implementation effort.
The JS community can't even be trusted to be stewards of a left pad library, never mind UI environments.
Designers.
End users simply want a functional, working product. Polish on top is a nice added bonus, but these days it's been turned into the focal point of software development. A Teams/Slack-caliber project begins with product requirements, immediately followed by design and UI mocks - the software/tech always comes last.
A computer program is a tool to convert data from one form to another. FULL STOP. Unnecessary added complexity, on top of that data transformation, is wasted effort, wasted time, wasted energy.
Software development has caused so many problems for itself because of things like this. People forget so quickly that programming is not the job! Solving the data transformation problem is the job. Effort spent that does not solve the problem is wasted effort, and we've made a fucking industry that churns out far more waste than product.
Now it's all JS and Electron and every single complaint people used against Java is an order of magnitude worse and everybody seems to be happy about it.
Progress have definitely been going backwards.
So if you have an excel file open in teams (which can take up at least 10 seconds - which does speak to your comment!), and want to go back to a channel or chat, you're actually closing that file.
Granted you can open the Excel file not in teams, but this is just an example of how being locked in one window where the tabs aren't your open items, but rather possibly open items, is counter-productive.
That brings me to something else that I find strange, that with every new piece of Windows software over the last 10 years, it seems like Microsoft forgot that it's called "Windows" for a reason. The big deal about Windows was having multiple WINDOWS. And every time you take that away, you stray further from productivity. Don't even get me started on multi-monitor support over the years! /rant
The nearest IDE I can think of is kdevelop or jetbrains. kdevelop is disturbingly light, but jetbrains consumes considerably more resources than VSCode. (And for good reason. They tend to do more)
Moreover the ease of developing electron apps has opened the desktop ecosystem to web developers who more often tend to have bad habits because of how forgiving most web dev is.
If they are going to keep doing this they need a way to compile the things to native binaries. I don't know...something.
I personally get really kind of weirded out when I see simple software load Node. Adobe, I'm looking at you.
I'm really hoping that the cross platform dotnet stuff becomes a viable option now that the XAML stack has been open sourced.
Developers need to stop building slow applications. This is ridiculous. It's 2019 and software is slower than it was in the 90s.
It must take an enormous number of CPU cycles to execute simple tasks in an Election-based app. It's just incredibly inefficient. I heard similar things about Slack – that it was built on Node, maybe Electron, and was dog slow, especially to open. It's frustrating that developers are bringing the slowness of the web to the desktop. Just build proper desktop applications using native desktop APIs.