maui-safe-area

Configure per-edge safe-area handling for MAUI apps across Android, iOS, and Mac Catalyst.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide explains how to manage cross-platform safe areas in MAUI, enabling precise per-edge control over device insets, notches, and keyboards to support edge-to-edge designs without content being obscured.

Core Features & Use Cases

  • Per-edge SafeAreaEdges and SafeAreaRegions for granular layout behavior across Android, iOS, and Mac Catalyst
  • Keyboard-aware layouts with SoftInput handling to keep input fields visible
  • Clear migration guidance from legacy ios:Page.UseSafeArea and IgnoreSafeArea
  • Blazor Hybrid CSS safe-area interoperability for web-based MAUI apps

Quick Start

Create a ContentPage with SafeAreaEdges=None to render content edge-to-edge on all devices.

Frequently Asked Questions about maui-safe-area

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

FAQPage Schema
How do I configure per-edge safe area insets in .NET MAUI?

Per-edge safe area insets in .NET MAUI are configured using SafeAreaEdges and SafeAreaRegions to control padding on individual sides of ContentPage and Layouts across Android, iOS, and Mac Catalyst.

Why does my MAUI content get obscured by notches and system bars on iOS?

Content gets obscured when legacy ios:Page.UseSafeArea or IgnoreSafeArea settings conflict with modern safe area handling, requiring migration to SafeAreaEdges for proper notch and system bar avoidance.

Can I use safe area handling in MAUI Blazor Hybrid apps?

Yes, safe area handling works in MAUI Blazor Hybrid apps through CSS safe-area interoperability, allowing web-based MAUI apps to respect device insets and achieve edge-to-edge layouts.

What's the best way to keep input fields visible above the keyboard in MAUI?

The best way to keep input fields visible is using keyboard-aware layouts with SoftInput handling, which adjusts ScrollView and Layout positioning to prevent the keyboard from obscuring active input fields.

Does maui-safe-area support edge-to-edge rendering across all platforms?

Yes, it supports edge-to-edge rendering across Android, iOS, and Mac Catalyst by setting SafeAreaEdges to None on ContentPage, allowing content to extend fully while still respecting notches and system bars when needed.

How do I migrate from ios:Page.UseSafeArea to modern MAUI safe area handling?

Migration from ios:Page.UseSafeArea involves replacing legacy properties with SafeAreaEdges and SafeAreaRegions configurations, enabling per-edge control and cross-platform runtime inset reading instead of iOS-only boolean toggles.