Jump to content

Mobile DevOps

Add links
From Wikipedia, the free encyclopedia

Mobile DevOps is a set of practices that applies the principles of DevOps specifically to the development of mobile applications. Traditional DevOps focuses on streamlining the software development process in general, but mobile development has its own unique challenges that require a tailored approach.[1] Mobile DevOps is not simply as a branch of DevOps specific to mobile app development, instead an extension and reinterpretation of the DevOps philosophy due to very specific requirements of the mobile world.[2]

Rationale

[edit]

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. The traditional DevOps approach primarily evolved to meet the changing needs of the software development world with the paradigm shift towards continuous and rapid development and deployment (such as in web development, where interpreted languages are more prevalent than compiled languages).[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.[5] This difference in the mobile development mindset compared to what the traditional DevOps approach is advocating, is augmented further with the mobile applications to be deployed on a high number of varying devices and operating systems.[6]

Eventually, the concept of Mobile DevOps took off as a trend around 2014-2015,[7] in line with the fast growth of the number of applications in mobile app stores.[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]

Mindset shift from traditional DevOps to mobile DevOps

[edit]

Mobile DevOps has a unique set of challenges and constraints, which solidifies the fact that it needs to be approached as a separate discipline.[1][9]

These challenges can be outlined as follows:

  • Platform-specific requirements and tight controls of mobile operating system providers, where for instance a macOS device is mandatory for iOS application development and release.[2][5]
  • The walled-garden approach of distributing mobile apps, specifically applying to iOS applications,[10] which comes with app review and app release delays that would not be needed in web development, for instance.
  • Code signing requirements that come with the walled-garden approach, which introduce additional processes in the mobile application build pipeline along with new security concerns.[5]
  • An entire deployment cycle is re-run even in the slightest code change due to how applications are compiled and delivered to the users.[5]
  • The final product is to be deployed to a wide variety of mobile devices worldwide, which requires extensive testing and user feedback.[9]
  • Monitoring mobile applications require additional tools and approaches to be able to get data from an application running on a mobile device while respecting user privacy.[1]
  • Frequent operating system updates by mobile platforms can require rapid adaptation of apps, introducing further complexity to the development and maintenance cycles.

Benefits of mobile DevOps

[edit]

Mobile DevOps is not an abstract concept and offers a range of benefits that can help improve the efficiency and effectiveness of the mobile app development process. These benefits can even be quantified by collecting the data within the mobile application development lifecycle.[9]

The benefits can be categorized into the following areas:

  • Faster Release Cycles: By automating tasks and streamlining the development process, mobile DevOps enables teams to deliver new features and updates more frequently.[9]
  • Improved Quality: Automated testing and continuous monitoring help to identify and fix bugs earlier in the development cycle, leading to higher quality apps.[1][6]
  • Optimized Resource Utilization: Mobile DevOps promotes optimized resource utilization by automating tasks and streamlining workflows. Furthermore, mobile DevOps practices like containerization can help to create more efficient and scalable development environments.[11]
  • Increased Agility: Mobile DevOps allows teams to be more responsive to changes in the market and user feedback.[11]

List of Dedicated Mobile DevOps Platforms

[edit]

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]).

To overcome the mobile-specific challenges specified, there are certain platforms that are dedicated to the lifecycle of mobile applications. These platforms exclusively focus on DevOps processes for mobile app development and are also referred as mobile CI/CD platforms.

  • Appcircle (Multiplatform | Cloud-based & On-premise)
  • Visual Studio App Center (Multiplatform | Cloud-based)
  • Xcode Cloud (Apple platforms only | Cloud-based)

See also

[edit]

References

[edit]
  1. ^ a b c d e Tak, Rohin; Modi, Jhalak (2018). Mobile DevOps: Deliver continuous integration and deployment within your mobile applications. Packt Publishing. pp. 12–18. ISBN 9781788296243.
  2. ^ a b "What is Mobile DevOps in iOS and Android App Development?". ionic.io. 2022-09-28. Retrieved 2024-03-26.
  3. ^ Atlassian. "History of DevOps". Atlassian. Retrieved 2024-03-26.
  4. ^ Smith, David (2024-01-25). "The Evolution of DevOps". DevOps.com. Retrieved 2024-03-26.
  5. ^ a b c d Appcircle (2022-10-08). "5 Differences Between Mobile CI/CD and Web/Backend CI/CD". Appcircle Blog. Retrieved 2024-03-26.
  6. ^ a b Yarlagadda, Ravi Teja (2019). "How DevOps Enhances the Software Dévelopment Quality". SSRN Electronic Journal. 7 (3): 358.
  7. ^ "Google Trends for the keyword "Mobile DevOps"". Google Trends. Retrieved 2024-03-26.
  8. ^ "Number of available apps in the Apple App Store from 2008 to July 2023". Statista. Retrieved 2024-03-27.
  9. ^ a b c d e Eramo, Romina; Soccia, Gian Luca; Noletti, Martina; Celi, Alessandro; Autili, Marco. "An Empirical Study on the Role of Devops in the Development of Mobile Applications". SSRN. doi:10.2139/ssrn.4719199.
  10. ^ Kirkwood, Megan (2024-02-06). "Regulating the Walled Garden: The Challenge of Taking on the Gatekeepers | TechPolicy.Press". Tech Policy Press. Retrieved 2024-03-27.
  11. ^ a b Nabil, Moataz (2023). Mobile DevOps Playbook. Packt. ISBN 9781803242552.
  12. ^ Bapat, Vaishnavi (2022-09-09). "Announcing macOS Runners in Bitbucket Pipelines". Bitbucket. Retrieved 2024-11-03.
  13. ^ "Building iOS Apps with Jenkins". Building iOS Apps with Jenkins. Retrieved 2024-11-03.
[edit]
Retrieved from "https://wiki.riteme.site/w/index.php?title=Mobile_DevOps&oldid=1259467450"