[2] Traditional DevOps approach has been formed around 2007-2008,[3] close to the dates when iOS and Android mobile operating systems were released to the public.
[4] While traditional DevOps embraced agility and flexibility, mobile operating system providers steered towards a walled-garden approach with compiled apps with tight controls over how they can be distributed and installed on a mobile device.
[8] As individuals and corporations alike are developing and publishing more and more mobile applications, the need for efficiency and shorter release cycles increased, which is addressed by the continuous feedback and continuous development approach within the concept of DevOps,[1] while requiring a significant level of adaptation and extension of the traditional DevOps practices.
[9] Mobile DevOps has a unique set of challenges and constraints, which solidifies the fact that it needs to be approached as a separate discipline.
[9] The benefits can be categorized into the following areas: Even though it is possible to run a mobile DevOps cycle with most of the CI/CD platforms, they may require significant effort compared to non-mobile CI/CD (e.g. you need to bring your own infrastructure[12] or it may require "reinventing the wheel" for commonly-used platforms like Jenkins[13]).