> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/connecting/apple-health-health-connect-and-mobile-sdk/samsung-health-connect-fallback-and-dev-mode.md).

# What can I test while Samsung approval is pending?

While awaiting Samsung partnership approval, you can develop and test against **Health Connect** as a drop-in. It supports the same data types as Samsung Health.

For local testing only, enable **Samsung Health Dev Mode** by tapping the version number repeatedly in Samsung Health settings. No Samsung Client ID or access code is needed for this step. The Client ID is part of Samsung's separate commercial partner programme, managed entirely on Samsung's side.

After approval, switch to the **Samsung-custom branch** of the SDK (e.g. `terra-react` tagged `samsung-custom`), which connects to Samsung's Health Data SDK rather than Health Connect. This is a separate SDK branch, not a version downgrade, so a lower version number than the standard line is expected.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/connecting/apple-health-health-connect-and-mobile-sdk/samsung-health-connect-fallback-and-dev-mode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.