Skip to main content

Open-WebUI-Functions is here! New Pipelines, Filters, and more. Learn more

Launch Other Android Apps from .NET MAUI

Launching another Android app from .NET MAUI requires declaring which packages you intend to query and handling the case where the app is unavailable. Starting with Android 11, you must opt into package visibility to query other installed apps.

Learn more

Overview

  • Declare every package you plan to launch inside the <queries> element of AndroidManifest.xml.
  • Use PackageManager.GetLaunchIntentForPackage to obtain the default activity intent.
  • Provide a fallback (such as opening the Play Store listing) when the app is not installed.

Prerequisites

  • Android target API level 30 or higher
  • Knowledge of target package names (for example com.contoso.app)
  • User messaging that explains why you launch external apps

Configure manifest queries and launcher logic

Caution

Declare every package explicitly. Wildcard queries are ignored on Android 11+.

Use Launcher.TryOpenAsync with market://details to deep link into the Play Store without blocking if the store app is missing.

Best practices

  • Security: Validate the package name against an allow-list so malicious input cannot open arbitrary apps.
  • User experience: Show a confirmation dialog when switching contexts, and clarify how to return to your app.
  • Error handling: Surface actionable messages when the target app is missing or disabled; offer to open the Play Store or provide alternate workflows.
  • Telemetry: Track launch success and failure reasons so you can maintain accurate partner lists.