maui-safe-area

Configure per-edge safe area insets for .NET MAUI applications across iOS, Android, and Mac Catalyst.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/heldercsousa/MyVocaList --skill maui-safe-area-heldercsousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-safe-area
Source: https://github.com/heldercsousa/MyVocaList/tree/main/.claude/skills/maui-safe-area
Command: npx skills add https://github.com/heldercsousa/MyVocaList --skill maui-safe-area-heldercsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MAUI developers often struggle with safe area handling across platforms, leading to content being obscured by system UI or keyboards. This Skill provides a cross-platform approach to edge-to-edge layouts and per-edge safe area configuration for .NET MAUI (.NET 10+).

Core Features & Use Cases

  • Safe per-edge control via SafeAreaEdges and SafeAreaRegions to tailor insets for headers, content, and footers.
  • Platform-specific behavior notes for iOS, Android, and Mac Catalyst, including migration guidance from legacy APIs.
  • Practical usage scenarios including immersive headers, keyboard-aware layouts, and Blazor Hybrid considerations.

Quick Start

Set the ContentPage SafeAreaEdges to None for edge-to-edge rendering, and apply per-edge SafeAreaEdges on layouts to tailor insets.

Frequently Asked Questions about maui-safe-area

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

FAQPage Schema
How do I handle safe area insets for edge-to-edge layouts in .NET MAUI?

Safe area handling for edge-to-edge layouts in .NET MAUI is done by setting the ContentPage SafeAreaEdges to None for full-screen rendering, then applying per-edge SafeAreaEdges on individual layouts to tailor insets for headers, content, and footers.

How does keyboard avoidance work across iOS and Android in MAUI applications?

Keyboard avoidance across iOS and Android in MAUI applications is managed through cross-platform safe area handling, which adjusts content insets dynamically so input fields remain visible above the on-screen keyboard.

Can I configure safe area insets per edge instead of applying them to the whole page?

Yes, you can configure safe area insets per edge. The solution defines SafeAreaEdges and SafeAreaRegions, allowing you to specify exact inset behavior for individual edges rather than applying a uniform safe area to the entire page.

Does this safe area approach work with Blazor Hybrid apps in .NET MAUI?

Yes, this safe area approach works with Blazor Hybrid apps in .NET MAUI. The solution explicitly documents practical usage scenarios including immersive headers, keyboard-aware layouts, and Blazor Hybrid considerations.

What's the best way to migrate from legacy safe area APIs in .NET MAUI?

The best way to migrate from legacy safe area APIs in .NET MAUI is to use the provided migration guidance, which documents platform-specific defaults and behavior across iOS, Android, and Mac Catalyst to ensure a smooth transition to SafeAreaEdges.

Why does my MAUI content get obscured by the notch and system bars on Android?

Your MAUI content gets obscured by the notch and system bars on Android because edge-to-edge visuals lack proper inset handling. Applying per-edge SafeAreaEdges ensures content avoids being covered by system UI elements like notches and navigation bars.