Appdome is a no-code mobile integration platform as a service (iPaaS), allowing users to integrate (Fuse) mobile services to Android and iOS apps.
This Knowledge Base article describes how Fusion automates integrating mobile SDKs to mobile apps. In other words, what’s happening under the covers when you click the big green magical “Fuse My App” button.
We hope you find it useful and enjoy using Appdome!
Integrating Mobile SDKs to Mobile Apps
Appdome is built to enable mobile developers to add mobile services, features, SDKs or APIs to mobile apps. Appdome is codeless, so you don’t need to be an app developer and you don’t need to write a single line of code to complete integrations. You don’t even need access to the source code to integrate services or SDKs with your mobile app. There are no special requirements, skill sets, dependencies. Simply put, Appdome makes the process of integrating mobile SDKs to mobile apps easy. Appdome is mobile integration for anyone. Appdome is cross-platform and has no framework or development environment dependencies. All you need to integrate features, services, or SDKs to your app are compiled app binaries (.ipa or .apk) and an Appdome account (which you can open for free, with no risk or obligation).
Creating an account on the Appdome platform is easy. Once you’re in, the Appdome Platform enables you to integrate new functionality and 3rd party SDK/APIs to your mobile apps instantly. Examples of the integrations available on Appdome are EMM, MDM, MAM, analytics, Enterprise Authentication, SSO, MFA, Mobile PKI, Cloud identity, messaging, collaboration, engagement, and more. When you fuse an SDK to an app, the outcome is much the same as you would achieve via manually implementing the service in source code; except on Appdome, you don’t need access to source code, and all integrations take between 30 seconds and a minute. All integrations on Appdome are completed to the compiled app binary, using Appdome’s patented method of binary app integration. Each integration leverages re-usable microservice adapters, which the platform combines with the existing app binary to form a new fully integrated, fully productized app binary. The fusion adapter becomes a part of the new app and ensures that the right function or API call is invoked at the right time, honoring the selections that the customer made during the fusion process and bridging any incompatibilities that may exist in the SDK. The end result is a natural set of interactions which does not alter the app’s design, interfere with the native OS function, or spoil the user experience. On Appdome, any changes in app behavior are expected and intended, vis a vis the selections the customer made during Fusion. This combined resource bundle can include both your app’s UI and the UI elements that are contained in the mobile service SDK.
For example, if the mobile SDK contains components that are required to run before the application loads (such as an EMM SDK that displays a provisioning screen) the Fusion Adapter will orchestrate the app-SDK priority so that the right component will be called before any other line of code of the original application.
The last stage of the Fusion process involves sealing the .apk or .ipa with ONEShield by Appdome, which is designed to protect the fused app from attempts at tampering, reverse engineering, or methods of compromise.
If you want to add other services or SDKs at a later time, you can fuse the app as many times as you like. Appdome never changes the original app binary. Since the process is so quick, often measured in minutes, the impact on your development cycle is negligible.
For more information Integrating mobile SDKs to mobile apps, please read the platform datasheet.
To zoom out on this topic, visit the Appdome Platform section on our website.