Teams is supposed to fix everything... but my O365 tenant doesn’t have it yet.
edit: "All" they did was come along at the right time and make the interoperability easy. The prerequisites to have done it at all? Smartphones, WebRTC, and ElasticSearch.
I wonder if we need a new word for "interoperability in the time of SaaS" - the kind of where SaaSes talk to other SaaSes via locked down APIs, under absolute control of the vendor.
In order to do what Slack is doing, they have to be somewhat committed to open standards. They are just doing webhooks, like GitHub does. We tried specifying microformats, and we tried specifying webhooks, but the "loose RPC" model... Seems to work way better than XMPP server interoperability ever has.
I recommend this recent nested Twitter ("new crowd") thread amongst Stewart Butterfield and many other early web folk, about whether Slack is a web app: https://twitter.com/stewart/status/961704310613491712
Capturing email, files and love communication drives subscription revenue for E5 SKUs of 365, plus most companies will need Azure AD to meet their security and compliance requirements.
We ran the numbers at work... taking the blue pill and going all on Microsoft will 3x our lifetime value to them vs a standard E3 shop.
One of my colleagues pointed out that the IM client from Exchange 2003 era (I think it was Live Communications Server) and LiveMeeting were a better collaboration platform than SfB, even given the severe limitations on bandwidth and cpu.
We recently switched to it for a world wide support team and it's a step down.
- No direct quoting, only threaded replies in group chats.
- No linking to Threads, even though you can personally bookmark it
- No message indications except in 1 on 1 chats ad hoc chats, so if you're in a large group thread, you have no idea if someone is paying attention or not
- Poor UI decisions (the menu which appears over messages for "options/bookmark/like" will obscure messages if the same user sent two messages in a row; because it appears over the right-most part and the second of two messages from the same user doesn't include the user info, the menu will hide whatever's at the end of the message).
- Scrolling back in a message thread (group or personal) is pointless, as messages take so long to load, and it seems to load sequentially. (i.e., you can't just scroll to approximately where you think the message is; if you scroll for 10 minutes, it will still just load the most recent messages before continuing)
- Search has no proper way of search only one conversation, it's all or nothing.
- The mobile app is incredibly slow to sync regardless of whether it's on data or wireless.
I could go on for awhile on this. I honestly wonder if anyone at Microsoft even tried to use Teams before they released it, since everything about it feels like it was just tossed in there and the devs weren't allowed to look at what other collaborative chat apps did to make them good. Even their "me too" implementation of things like giphy integration or inserting photos in to the chat is very poor (dragging a photo from desktop will insert it into the thread, but dragging it from the web will upload it to sharepoint, though both take very long to upload). Accessing Sharepoint content takes a long time because Microsoft's login to the Office 365 space takes a long time. All text is actually rich text, but for some reason they included a pseudo markdown syntax which just toggles the rich text functions (bold, italics, etc) whether you mean to or not. You can't just escape these characters either since it's not that well thought out of a function.
When we briefly had Skype For Business, I thought that Microsoft couldn't do any worse, but they really did their homework for Teams and made a real horrible product that works for basically no one.
On Linux it does not even show the screen shared by others (Windows) users. In the old Skype (not for Business) client Linux users could even share. For corporations progress means removing working functionality.