Adding controls to a mobile app is not easy. The apps’ source code may not be available, which is a common issue with third-party ISV apps. Mobile app developers may be unavailable to write code to integrate the SDKs and libraries that enable the additional controls. Or the app and the SDKs may use incompatible development frameworks.
The no-code integration workflow included with a Blue Cedar adds controls to mobile apps without requiring developers, source code access or compatibility between the development frameworks used by the app and the SDKs and libraries being integrated.
The example below is for conceptual purposes only.
Having multiple unified endpoint management (UEM) solutions are not uncommon: an acquired company uses another UEM, or transitioning to a new UEM requires running both for a period of time. Supporting multiple UEMs is challenging. Developers need to integrate multiple mobile application management (MAM) SDKs into apps. App distribution is also more complex, requiring publishing apps to multiple enterprise mobility management (EMM) catalogs and public app stores.
The apps for multiple UEMs workflow performs post-build adaptations to produce multiple app variants, each of which is compatible with a different UEM. Blue Cedar’s no-code integration service is combined with app import, scanning, signing, and distribution into a multi-branched deployment workflow. Custom coding isn’t needed and security processes are preserved.
Blue Cedar’s no-code integration workflow makes it simple to add controls to mobile apps without requiring developers, source code access, or compatibility between the development frameworks used by the app, the SDKs, and libraries being integrated.
The example below is for conceptual purposes only. It does not reflect the only 3rd party platforms supported.