A Capacitor plugin to open native Android and iOS system settings screens from hybrid mobile apps.
Capacitor Native Settings is a plugin for the Capacitor runtime that allows developers to open native system settings screens from within their hybrid mobile applications. It solves the problem of needing to guide users to device settings for permissions, configurations, or troubleshooting without requiring them to manually navigate the OS settings menu. The plugin provides a JavaScript API that maps to platform-specific intents and URL schemes.
Mobile developers building cross-platform apps with Capacitor or Ionic who need to programmatically direct users to system settings for app configuration, permission management, or device setup.
Developers choose this plugin because it offers a simple, unified API for a common mobile development task, saving time compared to implementing platform-specific native code. It is well-maintained across multiple Capacitor versions and provides clear documentation about platform limitations.
Capacitor plugin to open native settings screens for android and iOS
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Explicitly supports Capacitor versions 3 through 8 with clear version mapping, ensuring compatibility with a wide range of existing projects without forcing upgrades.
Provides detailed enums like AndroidSettings and IOSSettings with dozens of options (e.g., Accessibility, BatteryOptimization, VPN), covering most common use cases directly from the API.
Clearly warns in the README that only app-specific settings are officially supported on iOS, helping developers avoid App Store rejection by making informed decisions.
Offers simple methods like open(), openAndroid(), and openIOS() with type-safe interfaces, reducing boilerplate code for handling platform differences.
For most iOS settings beyond the app-specific screen, the plugin uses undocumented URL schemes that Apple can break at any time, risking app functionality and store approval.
It only launches settings screens; developers cannot read current settings values or programmatically change them, limiting utility for automated workflows.
Some Android settings, like ZenModePriority, may not work on all devices as noted in the README, leading to inconsistent behavior across manufacturers and OS versions.