Early stage companies are constantly evolving their product to fit the market they operate in. They reach customers to keep them engaged using a high magnitude vector that contributes to their success. Architecting the communications strategy for your product thus becomes an important problem to tackle, which in turn can cause second-order effects like having to trade off the speed of product development iterations.
In the last few months, we have been working on a new Apps framework for developers. The idea behind this framework is to make it easier for more developers to integrate external applications or their own applications into Mattermost. But wait a moment, don’t we have Plugins for that? Yes, but Apps provide some advantages to developers over Plugins.
Making sure your software and its documentation is accessible is not only the right thing to do, it’s the smart thing to do—and it’s actually not that difficult. An accessible product is as usable as possible for everyone, regardless of their physical and cognitive abilities. For example, blind people should be able access your documentation with a screen reader, and neurologically atypical people shouldn’t be distracted by flashing screens, pop-ups, or carousels.
How salespeople use Slack to leverage the power of their entire organisation.