This I think is third revision of API for slack?<p>That said - I really like the idea of a relatively straightforward way to wire up actions. I'd especially love to be able to get into and out of a database.<p>I starred another project - retool as well with an eye towards those quick crud apps that used to be basic WinForms + database server for windows users.
This is probably the worst announcement from a big company I ever saw. No word about use cases or advantages. It’s not even clear what is a platform for Slack.
FWIW, Slack's page about this is a lot more interesting: <a href="https://api.slack.com/future" rel="nofollow">https://api.slack.com/future</a>
I built a slack app today and it was a lot harder than it should have been. Event payloads are really inconsistent (one even is a JSON object encoded in a form data field), data about users is inconveniently hidden, and building a functional home tab with navigation is just annoying.<p>This looks like it might solve some of that. The deployment side of things looks awesome, and the typescript types will really help with the inconsistent event structures.
However I’m not sure if they are not cutting out a huge part of their target audience with their approach to hosting. How would I connect to an internal service or database with this? I can’t, which makes it super inconvenient for “quick company specific workflows”, which seems to be exactly what they are targeting.<p>That being said, I love the idea of Slack becoming a GUI for an event bus connecting various things together.<p>URL should also be changed to <a href="https://api.slack.com/future" rel="nofollow">https://api.slack.com/future</a>
I really wish I could use only e-mail instead of Slack/Teams for anything related to my day-to-day job. Both can stay for calls and ceremonies, but that's it. No messaging, no million other sub-applications in Slack/Teams that connect and integrate to everything. I find the whole thing truly tiresome to use.