> For the complete documentation index, see [llms.txt](https://handbook.mattermost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.mattermost.com/operations/research-and-development/product/release-process/mobile-release.md).

# Mobile app release process

The Mattermost team works on a monthly mobile app release process, with a new version submitted to the iOS App Store and Google Play Store on the 16th of each month.

Please refer to [the Mobile Release Playbook](https://community.mattermost.com/playbooks/playbooks/yxb6yyckgbrebe8eiuzmb6w8co/outline) for the release checklist.

**Note: iOS App Store approval may take a few days after the 16th.**

## Release Timeline

Note: T-minus counts are measured in "working days" (weekdays, Monday through Friday, excluding [the listed statutory holidays](https://handbook.mattermost.com/operations/workplace/people/working-at-mattermost/paid-time-off#holidays)) prior to release day.

The Mobile app release schedule follows the cloud/self-hosted release schedule to align all release testing cycles.

**Schedule for Mobile App releases**:

* Feature Complete at T-24
  * This is the Feature Complete deadline for the release.
  * Cut the release branch based off the `main` branch.
* RC-1 cut at T-19
  * Cut RC builds based off the release branch for QA release testing. Release testing begins.
  * Note: More frequent RC builds may be requested by the QA team and the Release Manager as we get closer to the release date and as more regression fixes get merged.
* Code Freeze at T-10
  * Release testing is completed.
  * [QA approval](https://community.mattermost.com/playbooks/playbooks/9znffdsm9p8ixpanycpnb1mwkh/outline) should be ready by T-10.
* Release Day at T-0


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.mattermost.com/operations/research-and-development/product/release-process/mobile-release.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.