Native Meeting SDK Multi Platform

When to Use

• You are shipping a shared meeting feature set across multiple native clients.
• You need consistent auth/signature and role policy across platforms.
• You need version-drift guardrails and staged rollout checks per platform.

Skill Chain

1. meeting-sdk
2. meeting-sdk/android
3. meeting-sdk/ios
4. meeting-sdk/macos
5. meeting-sdk/unreal
6. oauth

Typical Flow

1. Standardize server-side signing and role policy once.
2. Validate default UI join/start baseline on each platform.
3. Add platform-specific custom UI features only after baseline parity.
4. Maintain a version matrix and run upgrade checks per platform before release.
5. Track contradictions between wrapper docs, package artifacts, and API references.

References

• Meeting SDK Root Skill
• Android Reference Map (opens in a new tab)
• iOS Reference Map (opens in a new tab)
• macOS Reference Map (opens in a new tab)
• Unreal Reference Map (opens in a new tab)