Which integrations are supported by Terra's mobile SDKs and when should I use the SDK versus the API?

Terra's mobile SDKs (React Native, Flutter, iOS, Android) are specifically designed for mobile-only integrations that don't have their own Web APIs. These SDKs support:

Supported Mobile-Only Integrations:

• Apple Health (iOS only)
• Samsung Health (Android only - direct integration)
• Health Connect (Android only)
• Google Fit (Android only - via Health Connect)

When to Use Mobile SDK vs API:

Use Mobile SDK for:

• Apple Health, Samsung Health, Health Connect, Google Fit
• Data sources that require device-level access
• Mobile-only integrations without web APIs

Use Terra's Health & Fitness API for:

• Garmin, Fitbit, Strava, Zwift, and other providers with web APIs
• Backend integrations
• Any provider requiring server-side credential handling

Understanding Dashboard Labels: When you see "API + SDK" on the Terra Dashboard, this means:

• API: Available through Terra's Web API (backend integration)
• SDK: Available through mobile SDKs (for mobile-only sources)

For providers like Garmin that show "API + SDK", use the Health & Fitness API from your backend with the Terra Widget for user authentication. The mobile SDK should only be used for the mobile-only sources listed above.