Tweaking My Slack App - Best Practices & Suggestions?

Hey everyone,
I’ve been working on a Slack app and have been customizing their starter kit a bit. It’s a NodeJS app built with BoltJS (Slack’s framework) and I’ve added TypeScript, Eslint, Prettier, and set up logging and error reporting.
On top of that, I improved the directory structure, added database support, and set up some deployment options. Next up on the roadmap: payment integrations and AI prompts.
Anyone else building Slack apps? Anything else you’d suggest tweaking or adding? I’m open to ideas!

6 Likes

Sounds solid so far! I’d definitely look into caching strategies depending on how many requests your app will be handling. Redis has worked well for me in similar projects, especially when scaling up.

5 Likes

Nice setup! Have you thought about using WebSockets for real-time communication? It might be overkill for some apps, but if you’re planning anything where instant updates matter, it could be worth considering.

4 Likes

Adding payment integration is a smart move. Just make sure to stay on top of security! I’ve used Stripe for Slack apps in the past and it was pretty smooth, especially with webhooks for notifications. Btw, kudos for thinking about deployment from the start—that’s where a lot of devs trip up.

3 Likes

Awesome work! I’d suggest adding feature flagging if you haven’t already. It can make testing and rolling out new features much easier without messing with your live users too much.

2 Likes

Looks like you’ve already covered a lot! I’d suggest integrating some kind of user analytics to track usage. Tools like Amplitude or Mixpanel could help you figure out which features are actually being used and refine your app further.

1 Like

If you’re adding AI prompts, you might want to check out OpenAI’s API if you haven’t already. It integrates well with BoltJS, and adding some natural language processing might take your app to the next level.