Get started
  • English
  • 简体中文
Official Site
Get started
  • English
  • 简体中文
Official Site
  • Get started
    • Quick start
    • Account system
    • Docking mode
    • Resource download
  • Concepts
  • Guides
  • Device capabilities & events
  • API reference
  • SDK and tools
  • Solutions
  • Platform and support
On this page
Mobile app
Cloud live
Desktop app
OAuth 2.0
Related

Choose an integration mode

Choose an integration mode

Pick one or more approaches that match your product. The table below reflects the current integration guidance.

Mobile appCloud liveDesktop appOAuth 2.0
ProtocolPrivate protocolHLS, RTMPPrivate protocolHTTPS, OAuth H5
Time to first frame1–2 seconds3–8 seconds1–2 secondsDepends on API
Stream latency1–2 seconds8–10 seconds1–2 secondsRTSP (see getStreamUrl)
Live previewSupportedSupportedSupportedSupported (authorized devices)
Recorded playbackSupportedNot supportedSupportedPer API capability
Two-way talkSupportedNot supportedSupportedPer API capability
Device configurationSupportedNot supportedSupportedPer API capability
Integration effortHighVery lowHighMedium (server + H5)
Typical timeline1–3 months1–8 hours1–3 monthsDays to weeks

Mobile app

Integrate OpenSDK in an Android or iOS app for provisioning, device control, live preview, recorded playback, and two-way talk. See Build a mobile app.

Cloud live

Create a live URL for a bound device and embed it in a web page, WeChat official account, or H5: HLS for quick embed; RTMP via createDeviceRtmpLive—see From AppId to cloud live. Streams typically use H.264 video and AAC audio. If your player cannot decode the stream, change the encoding on the device’s local management page (on the LAN where the device sits). See Cloud live concept and HLS cloud live.

Desktop app

Use the PC OpenSDK to build a desktop app with device control, live preview, recorded playback, and two-way talk. See Build a desktop app.

OAuth 2.0

Connect end users' own Imou Life devices after they confirm on the platform authorization page. Your server holds the OAuth project Secret Key, exchanges the authorization code for tokens, and calls Open APIs with the user's Ot_ token. See OAuth 2.0 authorization and OAuth authorization APIs. This is not the same as binding devices to your developer account or using sub-accounts.

To embed a player in a web page, use the light-application component. See Integrate the light application. Download packages from Downloads.

Related

  • Create an app
  • Downloads
Account system
Resource download