maui-platform-invoke

To call native APIs from shared .NET MAUI code, you define a common interface and provide per-platform implementations for Android, iOS, Mac Catalyst, and Windows. You then use dependency injection to register and resolve the correct platform-specific service at build time.

The best way to structure cross-platform native API calls in MAUI is using partial classes and conditional compilation. This separates cross-platform logic from platform-specific implementations, ensuring safe access to native APIs across multiple targets without scattering code.

Yes, this MAUI platform invoke pattern explicitly targets Android, iOS, Mac Catalyst, and Windows. It uses multi-targeting and dependency injection to safely expose platform features through common interfaces across all supported operating systems.

You register platform-specific services in MauiProgram by adding your cross-platform interface and its per-platform implementation to the dependency injection container. This allows the application to select and execute the correct native code path for the active platform at build time.

Using dependency injection for MAUI native API calls centralizes platform-specific services and improves testability. Unlike relying solely on conditional compilation directives, dependency injection provides a clean architecture that keeps cross-platform logic decoupled from platform-specific implementations.

Use partial classes to cleanly separate cross-platform logic from platform-specific implementations, and use conditional compilation when you need to safely access platform APIs within multi-targeted files. Both patterns work together to maintain a clean architecture in .NET MAUI.