ios-slim-bindings

Slim iOS bindings use Swift or Objective-C wrappers to expose a focused subset of a native library, generating a .NET binding project and xcframework for distribution. This avoids binding the full API surface required by traditional methods.

Slim bindings wrap only the required native APIs in Swift or Objective-C, avoiding the heavy API surface of traditional bindings. This approach generates a leaner ApiDefinition.cs and xcframework, reducing maintenance overhead for .NET MAUI teams.

Yes, the slim bindings workflow supports optional integration steps for both CocoaPods and Swift Package Manager. You configure the Xcode project to pull native dependencies before generating the .NET binding project and xcframework.

You generate ApiDefinition.cs by implementing a Swift or Objective-C wrapper, setting up the Xcode project, and running the binding generation workflow. This produces the C# binding project files needed to build the xcframework.

Yes, XcodeGen is supported in the slim bindings workflow for iOS. You can use it to configure and generate the Xcode project structure before running the binding generation workflow to produce the .NET binding project and ApiDefinition.cs.

You should avoid slim iOS bindings if your .NET app needs to access the entire API surface of a native library rather than a focused subset. Traditional bindings are better suited for comprehensive API exposure without custom Swift or Objective-C wrapper development.