nimeet Docs
中文

Client SDK Platform Matrix

Platform matrix with interface sizes, availability and links to every guide and API reference.

Generated from the public API definitions

Version v1.1.0 · Updated 2026-10-26 · revision 1

ni-meet client SDKs cover 16 platforms. Every platform shares one product semantic and an API aligned with Agora 4.x. The class names, methods, parameters, overloads, events and error codes in the API reference are generated at build time from the public interface definitions, so the documentation stays in sync with the SDK package.

Choosing a platform

  1. Pick the platform that matches your stack; interface size and availability are listed under “Platforms and interface size” below.
  2. Follow a platform name into its “quickstart and feature guide”, which covers prerequisites, install commands, getting a token, the join flow, events, error handling and troubleshooting.
  3. When you need exact signatures, open the “API reference” for the same platform: the complete set of methods, overloads, properties, events and enums.

One integration model

Every platform follows the same model:

  • One API: class names, method names, events and error codes are consistent across platforms, so moving between them is cheap.
  • Identical semantics: connection state machine, event order, reconnect backoff, token renewal, statistics definitions, error mapping, device enumeration, role switching and data-channel semantics.
  • Fails loudly, never silently: capabilities not supported in the current version return a clear error code instead of a fake success.
  • API decoupled from the media implementation: application code depends only on the public API, not on the underlying media engine.

Token provider chain (identical on every platform)

Every platform accepts the same three token sources, which can be combined into a fallback chain:

FormUsageWhen to use
endpointCall your backend (which ultimately lands on POST /v1/tokens)Most applications
callbackDelegate to the host app / IM getRTCTokenInfoScenarios that already have an IM system
staticPre-issued tokenTests and offline demos

Never ship customerSecret / appCertificate inside a client package: the client only receives { appId, rtcToken, rtcUid }. For the semantic details see AccessToken2 semantics.

Shared semantics checklist

Whichever platform you use, the following semantics are the same:

  • Event order: connection-state-change → user-joined → user-published → user-unpublished → user-left;
  • Disconnection: during CONNECTION_STATE.RECONNECTING media does not stop and tracks are not destroyed; only -112 requires joining again;
  • Mute with setEnabled(false), not setMuted;
  • Role switching: setClientRole('audience') stops local publishing automatically;
  • Statistics: the field definitions of getRTCStats() match Analytics metrics.

What each platform can do

  • Content Inspect, E2EE, channel media relay and client-side direct CDN push are not available in the current version; the corresponding methods return error code -4 (ERR_NOT_SUPPORTED).
  • Runtime capability on each platform follows the published SDK package; the interface definitions in the API reference do not imply that every interface is available at runtime.
  • Cocos Creator: interface definitions and binding notes are provided; runtime capability follows the published SDK package.

Platforms and interface size

Interface sizes are computed at build time from the public interface definitions, to help you choose a platform. Availability follows the published SDK package.

PlatformLanguageInterface versionInterfaces/classesMethodsOverloadsEnumsError codesAvailabilityReference
Web(browser)TypeScript4.24.963157168096✅ Generally availableAPI reference
Electron(desktop)TypeScript4.6.213757857814648✅ Generally availableAPI reference
AndroidKotlin4.7.0143654709526✅ Generally availableAPI reference
iOSSwift / Objective-C4.7.013264964915170✅ Generally availableAPI reference
macOSSwift / Objective-C4.7.012161261214470✅ Generally availableAPI reference
Windows(C++)C++4.7.014968871915849✅ Generally availableAPI reference
FlutterDart6.6.415061861815048✅ Generally availableAPI reference
React NativeTypeScript / Java / Objective-C4.6.414157757714848✅ Generally availableAPI reference
Unity(C#)C#4.6.214058861714848✅ Generally availableAPI reference
Unreal Engine(C++)C++4.5.114060362914546✅ Generally availableAPI reference
Unreal Engine(Blueprint)Blueprint / C++4.5.1904584581036✅ Generally availableAPI reference
Cocos CreatorTypeScript4.5.32636354✅ Generally availableAPI reference
Mini program(WeChat)TypeScript2.6.54324540✅ Generally availableAPI reference
Cocos2d-x(C++ binding)C++4.7.02434800✅ Generally availableAPI reference
C#(.NET)C#unknown12151952514446✅ Generally availableAPI reference
HarmonyOS(ArkTS)ArkTS4.6.3883173178640✅ Generally availableAPI reference

Total: 1623 interfaces/classes, 7156 methods (7332 overloads) and 1584 enums.

Next steps

  • Choose a platform: open that platform’s “Quickstart and feature guide” for prerequisites, installation, token, joining, events and troubleshooting.
  • Read the API: the same platform’s “API reference” lists every method overload, property, event and enum.
  • Troubleshoot: see error codes for connection, authentication and media failures, and the FAQ.

Generated by the documentation build pipeline · 2026-10-31 01:24:02 UTC · Documentation center v1.1.0.

Content follows the public API definitions.

ni-meet is a self-hosted RTC PaaS with a LiveKit-based media plane (Apache-2.0) and an Agora-compatible API.