What should I do to extend my workspace’s functionality? Submit a pull request, use integrations, or build a Rocket.Chat app?
Each of those options has its strengths and weaknesses.
Changing the source code is the most powerful way of extending Rocket.Chat, but not the simplest - you need to learn the code base, understand the code pattern and rules, submit a PR, and follow up on any changes requested to get it merged.
However, integrations allow you to write simple scripts that will be executed when a message is sent or received in a channel. They’re quick to learn and write, but their scope is limited.
Apps are the middle ground. They are much more powerful than integrations, allowing you to interact with the UI and execute custom routines on several triggers. They're more complex than learning the code base and can be distributed to our community via the marketplace.
Do I need to host my app somewhere to make it available to Rocket.Chat?
Not at all! Rocket.Chat apps are packaged and deployed to a workspace, and the system will take care of hooking the app up. Apps can be installed manually or via the marketplace.
Can I build and use an app even if it’s not published in the marketplace?
Absolutely! It’s recommended you use our Apps-Engine CLI tool to develop your apps, making it super easy to deploy your apps to your own Rocket.Chat workspace.
Does Rocket.Chat have a plugin framework?
No, we don't have a plugin framework.
What language should I use to write apps?
Rocket.Chat uses TypeScript only.
Is there a limit to the number of apps I can install?
For premium workspaces, there is no limit on the number of apps that you can install and use.
Community workspaces can enable up to 5 marketplace apps. Private apps can only be enabled in premium plans.