Book Image

Mobile DevOps Playbook

By : Moataz Nabil
Book Image

Mobile DevOps Playbook

By: Moataz Nabil

Overview of this book

To build mobile apps, you need to understand mobile-first features, tools, and processes that help you build, test, and release robust apps faster and more efficiently. The multitude of challenges stemming from mobile development's inherent complexities, including native iOS and Android app creation, cross-platform frameworks, and the implementation of scalable architectures within extensive teams, collectively contribute to a substantial number of obstacles that can significantly prolong the release process. This book will help you understand and implement the best practices of mobile DevOps for continuous integration, testing, delivery, deployment, and monitoring. You’ll explore different challenges faced by developers due to varied OSs, the unforgiving nature of mobile applications, and continuous updates to mobile phones and learn how to maneuver through these challenges. You’ll also get to grips with the latest trends while discovering the potential future of mobile DevOps, with valuable insights and guidance about integrating mobile development teams into your organization. By the end of this book, you’ll be well-equipped to successfully implement mobile DevOps and build fast, qualitative, and efficient mobile apps for your team or organization.
Table of Contents (18 chapters)
1
Part 1: Introduction to Mobile DevOps
5
Part 2: Implementing the Mobile DevOps Environment
9
Part 3: Monitoring, Optimizing, and Securing Mobile DevOps
13
Part 4: Moving Beyond Mobile DevOps and the Future of DevOps

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: It is not necessary to call sleep() repeatedly in your tests. Maestro waits for the content to load automatically (but not too long) when this process takes a long time.

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

[default]exten => s,1,Dial(Zap/1|30)
exten => s,2,Voicemail(u100)
exten => s,102,Voicemail(b100)
exten => i,1,Voicemail(s0)

Any command-line input or output is written as follows:

wget --quiet https://github.com/TestArmada/flank/releases/download/ v22.05.0/flank.jar -O /usr/local/bin/flank.jar java -jar /usr/local/bin/flank.jar firebase test android run

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “Select System info from the Administration panel.”

Tips or important notes

Appear like this.