---
title: "Mobile Release Process"
slug: "mobile-release-process"
updated: 2026-06-16T14:19:19Z
published: 2026-06-16T14:19:19Z
canonical: "docs.rocket.chat/mobile-release-process"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Mobile Release Process

Rocket.Chat’s mobile application is built with [React Native](https://reactnative.dev/). Refer to the [Rocket.Chat.ReactNative](https://github.com/RocketChat/Rocket.Chat.ReactNative/tree/develop) repository for details. You can also find the latest release details in the [Mobile release notes](/v1/docs/mobile-release-notes) document. This document covers the mobile app release process.

## Versioning

The app ships monthly to production (iOS and Android).

| Release type | Description |
| --- | --- |
| **Major release**: Increment in the first digit of the version, for example, `3.0.0` → `4.0.0` | This is a foundational upgrade that can introduce breaking changes, significant new or reworked features, performance improvements, or architectural changes. |
| **Minor release**: Increment in the second digit of the version, for example, `4.71.0` → `4.72.0` | Adding new or enhanced capabilities, UI, and UX improvements. May also include improvements in performance, stability, and security. |
| **Patch release**: Increment in the third digit of the version, for example, `4.71.1` → `4.71.2` | Bug fixes for regressions or defects in the current major or minor release, and security vulnerability patches. Patch releases do not introduce new features or intended behavioral changes. |

## Monthly release process

The team targets the end of each month for the production release. A typical release cycle looks like this:

1. Starting from the beginning of a month, PRs are merged into the `develop` branch for a fixed version. The build number increments with each merge.
2. Approximately seven days before the release, the `develop` branch is frozen and no new merges are made.
3. The builds are submitted for review to the Apple App Store and Google Play Store.
4. After approval, the develop branch is merged to `master` and the GitHub release is available.