Ask HN: Value of a custom slash-menu service for Slack?
I built a customizable, context-sensitive menu module in another Slack project, and I'm thinking of spinning it out into a separate app. Essentially, it would let any team set up a custom internal menu (help, docs, contact info, onboarding), callable via '/menu', without having to build or host their own bot. The menus are multi-level (use IM buttons to navigate paths like main menu -> help -> contacts) and can be set to serve different content to different roles/groups.
The question is whether menus are a problem anyone needs solved? We have menus in Slack apps to help with app-specific stuff, but would teams get use out of having team-specific menus?
I'm trying to decide if it's worth spinning the module out into a separate service (Menus-as-a-Service - we can make MaaS a thing!), or if this would just turn into Slackstore clutter.
No comments yet.