> For the complete documentation index, see [llms.txt](https://docs.secure-contacts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secure-contacts.com/documentation/ios-and-android-version-of-sca-in-comparison.md).

# iOS and Android Version in Comparison

Secure Contacts App (SCA) delivers a unified experience across iOS and Android platforms. Both versions integrate seamlessly with Microsoft Intune, Azure Active Directory (AAD), and Microsoft Authentication Library (MSAL), providing Mobile Application Management (MAM) capabilities and ensuring enterprise-grade security and compliance.

#### Platform-Specific Differences

* **Caller Identification**:
  * **iOS**: Uses Call Directory Extension (CDE) for incoming call identification **without syncing with the device’s local contacts**.
  * **Android**: Uses a secure contact provider for native caller identification, also **without syncing with the device’s local contacts**.
* **Enrollment Types**:
  * **iOS**: Supports BYOD and COPE scenarios with Intune App Protection Policies and Conditional Access.
  * **Android**: Supports BYOD, COPE, and Android Enterprise Work Profile, all with Intune App Protection Policies and Conditional Access.
* **Optional Features**:
  * **iOS**: Optional integration with the Contact Provider Extension (CPE) enables contacts in Siri, CarPlay, and other native apps.
  * **Android**: Native contacts integration and Android Auto support are available when using Android Enterprise Work Profile.

Both platforms share core functionalities, but these platform-specific differences ensure SCA leverages each OS’s unique capabilities to provide an optimized user experience.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secure-contacts.com/documentation/ios-and-android-version-of-sca-in-comparison.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.