Swift
We’ll be guiding you through integrating mbark into your iOS application with a series of steps. We recommend going through them in order, but feel free to skip around.

XCFramework

With the introduction of Xcode 12 and the M1 build target, it is no longer possible to build a single binary framework that can run on both the simulator and Apple devices. To resolve this, Apple has introduced a new type of framework called the XCFramework.
If your company is using Xcode 12, make sure that your dependency management system is also fully updated. Then, follow the integration guide normally as you use mbark’s XCFramework releases.
If your company has not yet started using Xcode 12, please contact us to learn how to access a non-XCFramework release.

Install Paths

Before you dive into integrating mbark there are a few decisions you should make to help guide your process:
  • Are you integrating a new App or an existing application?
  • Are you replacing an existing Server Driven UI (SDUI) SDK?
  • Do you plan to use multiple SDUI SDKs?
  • What integration path makes sense for you? CocoaPods, Swift Package Manager (SPM), or manual integration?
Thinking about the above questions will help to define the path you will take through this documentation.
If you are starting a new application and thinking about mbark, we recommend you follow the Swift Package Manager integration path. This path automates many of the steps you would otherwise have to do yourself.
If you have an established application then follow the path that most closely matches the processes you are already using to manage your project.
Copy link