Skip to main content

DevOps for mobile apps challenges and best practices

Challenges

  • Multi-platform support
  • Mobile apps as an enterprise front end
  • Continuous integration and continuous delivery
  • The app store
  • 'Pull' not 'push' deployment
  • For consumer apps, failure is not an option


10 best practices for mobile DevOps

  • Continuous integration and continuous delivery
    • Ensure end-to-end traceability across all assets
    • Practice continuous integration
    • Maintain separate build and integration areas for each native mobile OS SDK version supported
    • Use automated build and deploy scripts
  • Testing and monitoring
    • Test each build thoroughly with as much automation as possible, on simulated and physical devices
    • Virtualize and simulate backend services that are not available during mobile app testing
    • Monitor the performance of deployed mobile apps and backend services
  • Mobile app delivery
    • Employ centralized governance for mobile provisioning profiles, certificates, and API keys
    • Use a virtual app store to test device deployment
    • Convert user feedback into enhancement requests and user stories



Comments

Popular posts from this blog

Pattern: Riblets vs. VIPER

Engineering the architecture behind Uber's new rider app

Not being held back by our extensive codebase and previous design choices gave us the freedom where we otherwise would have made compromises. The outcome is the sleek new app you see today, which implements a new mobile architecture across both iOS and Android. Read on to learn why we felt the need to create this new architecture pattern, called Riblets, and how it helps us reach our goals.

The platforms share:

Core architectureClass namesInheritance relationships between business logic unitsHow business logic is dividedPlugin points (names, existence, structure, etc.)Reactive programming chainsUnified platform components
Each Riblet is made up of one Router, Interactor, and Builder with its Component (hence the name), and optional Presenters and Views. The Router and Interactor handle the business logic, while the Presenter and View handle the view logic.

Uber

Stetho - A Chrome debug bridge for Android applications

Stetho is a sophisticated debug bridge for Android applications. When enabled, developers have access to the Chrome Developer Tools feature natively part of the Chrome desktop browser. Developers can also choose to enable the optional dumpapp tool which offers a powerful command-line interface to application internals.

Facebook Github

WireMock

WireMock is a flexible library for stubbing and mocking web services. Unlike general purpose mocking tools it works by creating an actual HTTP server that your code under test can connect to as it would a real web service.

It supports HTTP response stubbing, request verification, proxy/intercept, record/playback of stubs and fault injection, and can be used from within a unit test or deployed into a test environment.

Although it’s written in Java, there’s also a JSON API so you can use it with pretty much any language out there.

WireMock.org