Six operating-system implementations
Native & Mobile Backends
Ship native dialogs from desktop to mobile and browser through one versioned boundary.
Explore source ↗Capability
TaskDialog/MessageBoxW, NSAlert, GTK with Zenity fallback, UIAlertController, Android AlertDialog, and a WebAssembly overlay implement the shared managed and native C ABI.
- 01
Windows, macOS, and GTK desktop backends
- 02
iOS and Android bridges
- 03
WebAssembly overlay
- 04
Stable native C header and ABI
How it composes
From intent
to working system.
Package
RID assets, AAR, XCFramework, or WASM module carry the platform implementation.
Resolve
Managed or native callers initialize the versioned ABI.
Dispatch
Thread and lifecycle rules move work onto the platform UI context.
Fallback
Capability matrices and logging explain adaptations and unavailable features.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package NativeMessageBox<PackageReference Include="NativeMessageBox" Version="VERSION" /><PackageVersion Include="NativeMessageBox" Version="VERSION" /># Managed applications resolve the packaged runtime asset.dotnet add package NativeMessageBox
# Native consumers include native_message_box.h and link# the nativemessagebox library for the target RID.Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.