# Doximity Mobile Releases Streamlined with Automation

DevFeed: [Doximity Mobile Releases Streamlined with Automation](<https://devfeed.tech/articles/doximity-mobile-releases-streamlined-with-automation-20026.md>)

Original publisher: [Read original article](<https://technology.doximity.com/articles/doximity-mobile-releases-streamlined-with-automation>)

Author: Doximity

Published: 2023-04-12T14:19:00Z

Content type: article

Language: en

Sources: [Doximity](<https://devfeed.tech/sources/doximity.md>)

Topics: [Automation](<https://devfeed.tech/topics/automation.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [continuous-deployment](<https://devfeed.tech/tags/continuous-deployment.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-apps](<https://devfeed.tech/tags/mobile-apps.md>), [performance](<https://devfeed.tech/tags/performance.md>), [production](<https://devfeed.tech/tags/production.md>), [releases](<https://devfeed.tech/tags/releases.md>), [versioning](<https://devfeed.tech/tags/versioning.md>)

## AI overview

This article describes how Doximity's mobile team automated its release process to move from a three-week cycle to weekly releases. The team achieved the weekly cadence in November 2021, and weekly releases later required zero developer overhead while QA controlled the process.

## Source excerpt

Releasing mobile apps to the store is inherently slower than web updates due to manual process overhead, such as versioning, packaging, and submitting to the App Store for review. While web developers have long enjoyed full buzzword-compliant Continuous Deployment, mobile teams generally use a defined release cadence, typically 2-4 weeks. The DORA metric, which stands for DevOps Research and Assessment, evaluates performance using four key metrics: Deployment Frequency (DF), Lead Time for Changes (LT), Mean Time To Recover (MTTR), and Change Failure Rate (CFR). These metrics are commonly used to gauge an organization's agility, efficiency, and ability to implement changes quickly. Organizations that excel in these areas tend to perform smaller, more frequent deployments. A few years ago, our mobile team was classified as a medium performer for deployment frequency and reported 47% for change rate failure, which should be from 0% to 15%. We knew we could do better. Doximity mobile teams historically used a three-week release cycle. However, the pace wasn't fast enough to quickly get new features out the door. As a result, almost every release would be delayed due to some "very important thing" that had to get in. We also had to do more patch releases to fix issues introduced in production, which were even harder to debug with so many changes in a single version. One of the essential features that forced us to accelerate our release cycle was the Dialer Video product. We launched Dialer Video soon after the beginning of the pandemic. We wanted to get something out and to iterate quickly to meet the needs of our doctors while they were going through a difficult time and learning to work remotely. In April 2020, we attempted to shift to a weekly release cycle to meet this demand. While some automation was in place, there was also a lot of overhead with each release, and the developers spent a significant amount of time just managing the process. We compromised on a two-