Rocket.Chat is an open‑source communication platform that provides a mobile client for Android devices. It lets individuals and teams exchange text messages, share files, and start voice or video calls without relying on a proprietary service. Because the core software is open source, organizations can host their own server or use a hosted instance, giving them full control over data storage and privacy.
After installing the app, you connect to a Rocket.Chat server by entering its URL and your login credentials. The server can be a public instance provided by a service provider or a self‑hosted installation that you manage on your own infrastructure. Once connected, the app synchronizes your account, channels, and message history. All communication is routed through the selected server, which handles authentication, message storage, and optional encryption.
Rocket.Chat is suitable for a range of scenarios:
The app is available through the standard Android package distribution. Open the Google Play Store, search for “Rocket.Chat”, and tap Install. After installation, launch the app and follow the on‑screen prompts to add your server address and log in.
Rocket.Chat runs on Android devices that support the Google Play services framework. Because the client is built with standard Android components, it works on a wide range of smartphones and tablets, regardless of manufacturer.
Anyone who prefers an open‑source alternative to mainstream messaging apps can benefit from Rocket.Chat. This includes developers, NGOs, educational institutions, and businesses that need to keep communication under their own administrative control.
Yes. The Android client is free to download and use. The underlying platform is released under the MIT license, which permits free use and modification.
The client requires a server endpoint to function. You can either join an existing public server or set up your own.
Yes. When connected to a server that has push notification support enabled, the app will deliver real‑time alerts for new messages and mentions.
Encryption depends on the server configuration. Many deployments enable TLS for data in transit, and some support end‑to‑end encryption for messages.









