In this blog post, we’ll round up the best mobile CI/CD advice from last year’s Mobile DevOps Summit to help you release better apps, faster. Our Agenda and Speaker list have been released for our 2023 Mobile DevOps Summit: October 4 - 5.

Secret management in shared environments like Continuous Integration and Delivery services is challenging. It’s essential to keep secrets secure and ensure they don’t end up in the wrong place, like logs or code repositories. Integrating solutions like 1Password into CI/CD workflows offer the advantage of centralising secret management, and it also allows you to encrypt every secret, providing controlled programmatic access to applications.

In Flutter’s early days in 2019, I developed a live object detection system for a major German company, despite the platform’s constraints. With release of Flutter 3.7 and advancements of TensorFlow have catalyzed the need to refine or overhaul this approach. This article discusses the newest techniques in live-stream object detection as showcased in the flutter-tflite GitHub repository.

Let’s start with some absolutes. Maintaining a steady CI/CD pipeline is crucial to modern software development. Testing and quality engineering principles that drive solid deliverables should be flexible and agile. QA teams need hundreds of device and O/S combinations. With those non-negotiables in mind, how would you implement a flexible device architecture to support ongoing and evolving needs to assess mobile and web applications?

Mobile developers using Javascript-based mobile application development platforms such as Cordova, Ionic and React Native have enjoyed the benefit of being able to push app updates over-the-air without resubmitting their apps to the App Store or Google Play for quite some time. As long as the updates are not compiled code, and don’t change the primary purpose of the application then both Apple and Google allow this.