|Read this if:||You're still experimenting, prototyping, and exploring.|
|Read next:||Plotting out interactive flows|
When you set out to make a Slack app, the range of possibilities can make you feel like you've stepped into Wonka's Chocolate Factory. If you're bewildered at the options in front of you, use this guide to choose from the delicious treats of the Slack platform.
While this guide presents a framework for planning a Slack app, it's by no means the only way. If you've chosen a course already, stay resolute. For the wandering, wondering remainder, this guide is for you.
Now is the time to figure out how your app will help make other people’s working lives simpler, more pleasant, and more productive.
Gather feedback and surveys from a diverse range of people within your organization. We don't prescribe the feedback or ideas to seek, but here are some thought experiments to try:
Storyboarding is a great way to help you figure out how people will interact with your app—and therefore to decide which features to implement.
Let’s walk through some planning exercises that will help you efficiently map out your app's interactions.
Put yourself in a user’s shoes. Imagine them trying to complete a specific task using your app. How do they make first contact?
Will it be easiest for them to initiate the workflow by using an custom message action, by calling a slash command, or by interacting with your messages? Or maybe your app should provide multiple entry points for the same workflow?
There is no single correct answer for every apps or every user. Take time to explore different possible ways of guiding a person through getting this work done, and picking whatever is simplest for your user base.
Read our guide to picking interaction triggers to explore this topic further.
Think about what happens after a user initiates a workflow. Imagine the series of messages that might be exchanged between user and app to reach a conclusion. And then do it again for different user personas.
This exercise will help you to figure out the kinds of messages you'll need to send, and the APIs your app might need along the way.
You might find that you can compress some workflows with clever interactivity, or use more assistive language in your messages to reduce confusion.
After storyboarding your app's workflow, you should have a better idea of what kind of functionality you'll need to implement—read our guide to choosing the right APIs to see how you can build those functions.
Slack users are people of all ages, races, genders, and ability levels. They may have poor internet connections, use Slack only on mobile, or they might never have used a Slack app before. We want them all to have a great experience on Slack, so be sympathetic of your audience when designing your app.
Read our interaction guidelines for further tips on building apps for diverse audiences.
After following the process outlined in this overview, you should have a good sense of your app's audience, and what the app will do.