android-slim-bindings

Build Android bindings for .NET MAUI by creating Java/Kotlin wrappers, configuring Gradle builds, and resolving Maven dependencies to generate C# binding layers using the Native Library Interop approach. This enables wrapping native Android SDKs and exposing them through a stable binding layer directly to .NET applications.

Native Library Interop (NLI) is a technique for bridging native Android libraries to .NET. It guides the creation of slim Java/Kotlin wrappers, manages Gradle builds, and resolves Maven dependencies to package AAR/JAR files for generating the final C# binding surface. This approach streamlines the integration of native SDKs into .NET MAUI projects.

Resolve Maven dependencies for Android AAR binding projects by configuring the Gradle project setup to manage and fetch required Java/Kotlin libraries. This ensures robust interop and correct AAR/JAR packaging before generating the C# binding surface and applying Metadata.xml transforms to expose the desired APIs to .NET.

Yes, you can bind a native Android SDK to a MAUI app by configuring Gradle and referencing AAR files. This process involves wrapping a small API surface in Java/Kotlin, resolving Maven dependencies, and applying Metadata.xml transforms to expose the desired APIs through a stable C# binding layer.

Slim Android bindings wrap only a small, necessary API surface rather than the entire native SDK, reducing complexity and maintenance overhead. By creating targeted Java/Kotlin wrappers and exposing them through a stable C# binding layer, you achieve robust interop without the bloat of binding unused APIs.