Should you track DORA metrics for mobile apps?
Blog post from Swarmia
DORA metrics, popular for tracking software delivery performance, may not align well with the unique demands of mobile app development due to the slower release cycles and complex deployment environment of mobile apps. High-performing mobile teams often adopt practices such as maintaining a steady release cadence, using prerelease versions for internal or beta users, and employing feature flags to manage feature rollouts independently of app release cycles. These strategies help in managing the costs and delays associated with app store reviews and user adoption. While DORA metrics focus on quick iteration without breaking things, they can be challenging to apply directly to mobile app development due to factors like slow user adoption of app updates and the need for extensive QA. Instead, mobile teams might benefit more from tracking metrics that reflect their specific processes, such as missed planned releases, hotfix frequencies, and automated testing efficacy. If DORA metrics are required, they should be tailored to suit the mobile context, focusing on internal/beta release channels to better reflect the team's continuous delivery capabilities.