maui-platform-backend

Implement .NET MAUI backend handlers and Essentials services for new platforms.

209|27|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill maui-platform-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-platform-backend
Source: https://github.com/dotnet/maui-labs/tree/main/.github/skills/maui-platform-backend
Command: npx skills add https://github.com/dotnet/maui-labs --skill maui-platform-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents stalled, error-prone platform work by giving a structured, end-to-end blueprint for implementing a new .NET MAUI backend in maui-labs, including core infrastructure, controls, Essentials services, and debugging guidance.

Core Features & Use Cases

  • Backend scaffolding & project structure: Create a self-contained backend under platforms/[Platform.Name]/ with the expected .slnx, src/, samples/, and NuGet-packable project layout.
  • Handler implementation roadmap: Follow phased steps to implement the base handler, dispatcher, MauiContext, app/window handlers, core layouts, and progressively add controls through interactive, navigation, and advanced features.
  • Platform parity & reliability practices: Apply key architectural principles (MAUI owns layout, property mapper drives updates) and avoid known anti-patterns that commonly cause crashes or rendering hangs.
  • Debugging workflow with DevFlow: Use the recommended audit and visual inspection loop to diagnose missing handlers, incorrect bounds, and property-mapping issues, including specific stop-signal guidance for stale process debugging.
  • Extensibility gap workarounds: Address known MAUI gaps such as Alerts/Dialog via DispatchProxy and Essentials SetDefault() via reflection, plus guidance on other registration bypasses.

Quick Start

Use this skill to scaffold and implement a new platform backend under platforms/[Platform.Name]/, then validate handler rendering and property updates with MAUI DevFlow before adding the rest of the control surface.

Frequently Asked Questions about maui-platform-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a new .NET MAUI backend for a custom platform?

To implement a .NET MAUI backend, you scaffold a self-contained project under `platforms/[Platform.Name]/` and follow a phased checklist to wire base handlers, dispatcher, and MauiContext. This maps virtual views to native types and sets up app/window handlers.

What is the best way to map virtual views to native view types in .NET MAUI?

The best way to map virtual views to native types in .NET MAUI is by implementing backend handlers and using the property mapper to drive updates. MAUI owns the layout, ensuring the backend receives correct bounds and rendering instructions.

How does DevFlow debugging work for .NET MAUI handler rendering issues?

DevFlow debugging for .NET MAUI handler rendering uses an audit and visual inspection loop to diagnose missing handlers, incorrect bounds, and property-mapping issues. It includes specific stop-signal guidance to handle stale process debugging effectively.

Can I use .NET MAUI Essentials services with a new platform backend?

Yes, you can use .NET MAUI Essentials services with a new backend, but you must bypass known extensibility gaps. This involves handling Essentials `SetDefault()` via reflection and addressing Alerts/Dialog registration through DispatchProxy.

Why does my .NET MAUI custom platform backend crash or hang during layout rendering?

A .NET MAUI custom platform backend crashes or hangs during layout rendering when violating the MAUI-owned layout rule or applying known anti-patterns. Enforce property mapper updates and use DevFlow to inspect handler bounds and identify missing mappings.