What problem does it solve?
Native Android SDKs often expose functionality only through Java/Kotlin (AAR/JAR/Maven artifacts), and .NET MAUI developers need a reliable way to make only the required APIs available to C# without wrestling with a huge, brittle full binding surface.
Core Features & Use Cases
- Create slim Native Library Interop wrappers: Build a thin Java/Kotlin wrapper that exposes only the APIs you want from a native Android library.
- Manage Maven/AAR dependencies for bindings: Analyze the full Gradle dependency tree, map Maven artifacts to the correct NuGet bindings, and handle missing transitive dependencies using .NET Android binding mechanisms.
- Generate C# bindings with metadata transforms: Use
Transforms/Metadata.xml to rename namespaces/parameters and remove or adjust problematic types so the generated APIs are usable from MAUI/C#.
- Update bindings as native SDKs evolve: Rebuild the wrapper AAR, refresh Maven/NuGet dependencies, and iterate on metadata transforms and troubleshooting until the binding compiles and runs.
Quick Start
Provide the Maven coordinates (or AAR/JAR source) of the Android library and ask the assistant to generate the minimal Java/Kotlin wrapper plus the corresponding .csproj configuration and Transforms/Metadata.xml strategy for producing slim Android bindings for .NET MAUI.