A Capacitor plugin for accessing, creating, and deleting native iOS and Android device contacts.
@capacitor-community/contacts is a Capacitor plugin that provides access to native device contacts on iOS and Android platforms. It solves the problem of building cross-platform mobile apps that need to read, create, or delete contacts by offering a unified JavaScript API that bridges to platform-specific contact databases.
Mobile developers using Capacitor to build hybrid iOS/Android applications that require contact integration, such as communication apps, social platforms, or productivity tools.
Developers choose this plugin because it offers reliable native contact access without writing separate iOS and Android implementations, is actively maintained with long-term support for multiple Capacitor versions, and comes from the trusted Capacitor Community ecosystem.
Contacts Plugin for Capacitor
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Bridges directly to iOS Contacts Framework and Android Contacts Provider for reliable, platform-specific contact operations, as highlighted in the README's key features.
Provides a unified JavaScript API that works identically across iOS and Android, enabling developers to maintain a single codebase for contact management without separate native code.
Actively maintained with long-term support for Capacitor versions v3 through v7, as evidenced by the version table and maintenance badge in the README.
Focuses on a stable, minimal API that allows quick implementation of contact features, aligning with the project's philosophy of reducing complexity.
The README explicitly states that web implementation is not included and must be handled separately, limiting true cross-platform coverage for hybrid apps.
Only supports retrieve, create, and delete operations; updating contacts or advanced functionalities like filtering by groups are not mentioned, potentially requiring custom work.
Past versioning strategies were inconsistent, as admitted in the README, which could cause confusion during upgrades or migrations despite current LTS support.