[apimade]

If this is just a replacement chat tool, it's fine - and a great start.

But if you want to replace Slack, you need to focus on the developer community and third-party integrations right now. We're not paying for something that only gives us "just" chat with better-by-design UX and chat workflows. Teams is free and fits this purpose, at least in the eyes of an executive.

Slack's developer environment (outside of Grid features, the new "Premium Workflows" and "Next Generation Platform") is first-class.

At the very least start with some webhook integrations.

Also your Privacy Policy has no mention of Amazon Web Services, I think you might want to review your "DATA PROCESSORS / SERVICE PROVIDERS" section.

Also, are you planning on offering single-tenant options? Not a fan of our chat data sitting with a bunch of other organisations.

[jesterson]

> We're not paying for something that only gives us "just" chat with better-by-design UX and chat workflows

Perhaps it is true from developer perspective, but from management perspective I welcome clear chat as it is without bells and whistles of countless integrations.

Slack at current state of events turned into colossal distraction and time waster.

All those integrations have nothing to do with comm platform IMO, they are well belong to other business processes.

[ryanjshaw]

> All those integrations have nothing to do with comm platform IMO, they are well belong to other business processes.

I think the market has spoken and your view is in the minority I'm afraid. There is a non-zero chance that Windows 2030 Enterprise will throw away the start menu, the desktop, the app store, File Explorer, etc. and replace it all with TeamsEdge (Teams + Edge).

[jesterson]

Whether it is market forces or just company shenanigans to make the product irreplaceable, can be a subject of a different discussion, albeit I tend to think of latter.

As the view being a minority, it’s true, no surprise to that in current paradigm.

[Lord_Zero]

Anyone in here ever heard of IRC or am I too old now?

[cheeseblubber]

Definitely agree on developer community and third party integrations. That is our main focus after this launch. Building just a good quality chat tool took quite a bit of time but we understand how important the dev ecosystem is.

Thanks for checking the privacy policy will update to include AWS!

[sverhagen]

Well... first class...? It's first class in the sense that it's proven good enough to help them to become successful. But in the meantime it's a hot mess of deprecations alongside unfinished thoughts alongside convoluted docs that give you a runaround. So, not first class APIs in the way developers speak about, for example, Stripe.