Part 1: Packaging Our iOS SDK as a Binary Framework

Context Recently, a client approached us to integrate a banking app SDK into their existing mobile banking application. While I can’t share all the details due to NDA restrictions, the challenge was straightforward on the surface: integrate an SDK. Easy! I thought to myself. However, the client’s requirements demanded a level of control and security that went beyond our standard CocoaPods integration. Most banking apps follow tight security standards to prevent any data breaches and compromise. So they tend to integrate external libraries differently. Instead of CocoaPods, they use frameworks, which provide more control over the code they “inject” into their applications. So, a new challenge on our hands. Enter the world of XCFrameworks: a modern approach to packaging code for multiple platforms, ensuring a single, self-contained binary that’s robust and future-proof (According to Apple). So a few terminologies as we begin: Library

Apr 13, 2025 - 17:42
 0
Part 1: Packaging Our iOS SDK as a Binary Framework

Context

Recently, a client approached us to integrate a banking app SDK into their existing mobile banking application. While I can’t share all the details due to NDA restrictions, the challenge was straightforward on the surface: integrate an SDK. Easy! I thought to myself. However, the client’s requirements demanded a level of control and security that went beyond our standard CocoaPods integration.

Most banking apps follow tight security standards to prevent any data breaches and compromise. So they tend to integrate external libraries differently. Instead of CocoaPods, they use frameworks, which provide more control over the code they “inject” into their applications.

So, a new challenge on our hands. Enter the world of XCFrameworks: a modern approach to packaging code for multiple platforms, ensuring a single, self-contained binary that’s robust and future-proof (According to Apple).

So a few terminologies as we begin:

  1. Library