Pular para o conteúdo principal

Choose an Integration

Choose by runtime responsibility: mobile device features belong in the Flutter SDK, user-scoped SDK integrations use the REST API, and app-wide server workflows use the Backend API.

Comparison

FeatureFlutter SDKREST APIBackend API
PlatformFlutter on Android and iOSAny client using an SDK user's identityServer-to-server backend or service
BLE device supportPairing, reconnect, typed device state, and commandsNot availableNot available
SOSFull SDK-owned lifecycle and capability selectionUser-scoped HTTP fallback or contracted MQTTNot part of this API
Realtime eventsManaged MQTT lifecycle and typed streamsDirect MQTT integration where contractedNot part of this API
Protection ModeAndroid-first, capability-aware runtimeNot availableNot available
OTA firmware updatesAvailability, blockers, transfer, reconnect, and verificationSDK integration endpointsNot available
LoRa radio regionCountry detection, confirmation, apply, reboot, and verificationSDK integration endpointsNot available
Users and devicesSDK profile and paired-device stateCurrent SDK user's dataApp-wide user, device, and linking management
TelemetryManaged device and location flowsCurrent SDK user's HTTP fallbackApp-wide ingestion, history, search, and batch writes
AuthenticationSDK manages signed user identityYour integration supplies SDK user headersApp-scoped Bearer credential with explicit scopes

Choose the Flutter SDK when the mobile app needs any device or safety runtime feature:

  • Direct BLE pairing with Eixam hardware
  • SOS, PRE-SOS, DMP, or Protection Mode
  • Managed realtime telemetry and device state
  • OTA firmware updates or regional LoRa configuration

Start here: Flutter SDK Overview