NativeChannelsNative APIs. One reusable bridge.

A small API for a native round trip ​

Register your native adapter once, then inject IChannelService into a service or view model:

using var channel = channels.GetMethodChannel("sample");
string? reply = await channel.InvokeAsync<string>("echo", "Hello from .NET");

The bundled Kotlin and Swift adapters return the same string. Native code can also call a managed handler and await its result. The getting-started guide includes package setup, module registration, and the complete application service.

Four contracts, practical examples ​

Each reference plugin has its own MAUI sample and local package workflow. See examples for setup, what each one teaches, and platform limitations.

Built around explicit lifetimes ​

Channel handles own their requests and registrations. Event enumerations own their subscriptions. Native view connections own their instances and channels. Cancellation, timeouts, errors, and UI dispatch are part of the contract.

Learn channel ownership · Configure requests · Handle failures

Find your next step ​

• Application developers: make a first call, then choose a channel.
• Plugin authors: design and package an integration, starting from the Currency example.
• Contributors: build from source, run tests, and review release checklist.

Android, iOS, Mac Catalyst, and Windows builds are supported through MAUI. Execution coverage and physical-device gaps are recorded in the verification matrix. Browse the guide index for the full documentation.