maui-safe-area

Configure .NET MAUI safe area edges for system bars and keyboard overlap.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill maui-safe-area-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-safe-area
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/maui-safe-area
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill maui-safe-area-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents your .NET MAUI UI from being hidden behind the status bar, notch/Dynamic Island, navigation bars, or the on-screen keyboard by providing correct edge-to-edge safe area handling.

Core Features & Use Cases

  • Per-edge safe area control (NET 10+): Use SafeAreaEdges and the SafeAreaRegions flags to apply safe-area behavior independently to left, top, right, and bottom.
  • Keyboard-aware layouts: Combine Container and SoftInput to keep content visible when the keyboard appears, especially for chat and form screens.
  • Cross-platform migration guidance: Migrate from legacy iOS-only UseSafeArea and layout IgnoreSafeArea patterns to the unified .NET 10+ API, including handling behavior changes like ContentPage default changes on Android.

Quick Start

Ask the AI: "Given my MAUI .NET 10+ ContentPage that should avoid the keyboard but go edge-to-edge behind the status bar, what SafeAreaEdges values should I set on the page and on the child layout?"

Frequently Asked Questions about maui-safe-area

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

FAQPage Schema
How do I prevent my .NET MAUI UI from overlapping the notch and status bar?

To prevent .NET MAUI UI overlap with the notch and status bar, apply edge-to-edge safe area configuration using SafeAreaEdges flags to independently control safe-area behavior for the left, top, right, and bottom edges.

How do I keep MAUI content visible when the on-screen keyboard appears?

To keep MAUI content visible when the on-screen keyboard appears, combine the Container and SoftInput safe area regions to enforce keyboard-aware layouts that prevent overlap on chat and form screens.

How do I migrate from legacy iOS-only UseSafeArea to the .NET 10+ MAUI API?

Migrating from legacy iOS-only UseSafeArea to the .NET 10+ MAUI API involves replacing IgnoreSafeArea patterns with unified SafeAreaEdges and SafeAreaRegions flags, while handling behavior changes like ContentPage defaults on Android.

Does the MAUI safe area API support Blazor Hybrid apps?

Yes, the .NET MAUI safe area API supports Blazor Hybrid apps by providing specific safe-area coordination for Blazor Hybrid screens during migrations and new screen designs to prevent system bar overlap.

What's the best way to apply safe area insets per-edge in a MAUI ContentPage?

The best way to apply per-edge safe area insets in a MAUI ContentPage is setting SafeAreaEdges values on the page and child layouts independently, satisfying specific edge requirements without legacy iOS-only APIs.

Why does my MAUI Android ContentPage layout behavior differ after migrating safe areas?

Your MAUI Android ContentPage layout behavior differs after migration because .NET 10+ enforces control-specific default behaviors and changes ContentPage defaults on Android, requiring unified SafeAreaRegions flags for proper edge-to-edge handling.