As of 2024, the Contact Picker API is primarily supported on Chrome for Android (version 80+). It also works in Edge on Android and some Chromium-based mobile browsers. Desktop browsers (Chrome, Firefox, Safari, Edge) do not support this API because they lack access to a system contact database. The API requires HTTPS or localhost for security reasons. You can check Can I Use for the latest support data.

Yes, the API is designed with privacy-first principles. The website never gets access to your full address book — only the specific contacts you manually select through the native system picker dialog. Key security features include: (1) Requires a user gesture (click/tap) to trigger; (2) Only works over HTTPS; (3) The browser's native picker UI ensures the website cannot stealth-read contacts; (4) Users can cancel at any time; (5) Only the requested properties are returned. The API does not allow background or automatic contact access.

The API supports five property types: name (ContactAddress with givenName, familyName, etc.), tel (array of phone numbers), email (array of email addresses), address (array of physical addresses with country, city, street, postal code, etc.), and icon (array of contact photo Blobs). Not all devices support all properties — use navigator.contacts.getProperties() to dynamically discover what's available. "name" and "tel" have the widest support across devices.

Absolutely! The Contact Picker API works great in PWAs. In fact, it's one of the key APIs that help bridge the gap between web apps and native apps. When your PWA is installed on Android via Chrome, the contact picker functions seamlessly. Make sure your PWA manifest is properly configured and the app is served over HTTPS. This enables use cases like inviting friends, sharing content, or filling forms with contact data — all within your PWA.

If the user cancels the picker dialog or denies permission, the navigator.contacts.select() promise rejects with an error. You should always wrap the call in a try/catch block and handle this gracefully — for example, by showing a friendly message that no contacts were selected. The API does not expose whether the user explicitly denied or simply dismissed the dialog, which is intentional for privacy. Never assume the user will always grant access.

The Contact Picker API (navigator.contacts.select()) is fundamentally different from older approaches: (1) It's a browser-native API — no plugin or Cordova required; (2) It uses a system picker UI so the website never sees the full contact list; (3) It's explicit opt-in per interaction — each select() call requires a fresh user gesture; (4) Older APIs like the deprecated navigator.contacts (Contacts API) allowed broader access and were removed due to privacy concerns. The new API is designed for the modern, privacy-conscious web.