build-zoom-meeting-app

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/build-zoom-meeting-app

/build-zoom-meeting-app

Use this skill for embedded meeting experiences and meeting lifecycle implementation.
本技能适用于嵌入式会议体验及会议生命周期的实现场景。

Covers

涵盖内容

  • Meeting SDK selection and platform routing
  • Join/auth implementation planning
  • Meeting creation plus join flow design
  • Web vs native platform considerations
  • Meeting SDK vs Video SDK boundary decisions
  • Meeting SDK选型与平台路由规划
  • 入会/鉴权实现方案规划
  • 会议创建及入会流程设计
  • Web与原生平台的考量因素
  • Meeting SDK与Video SDK的边界决策

Workflow

工作流程

  1. Confirm whether the user wants a Zoom meeting or a custom video session.
  2. Route to Meeting SDK if the user needs actual Zoom meetings.
  3. Pull in the relevant platform references.
  4. Add REST API only for meeting creation, resource management, or reporting.
  5. Add webhooks or RTMS only when the use case explicitly needs them.
  1. 确认用户需要的是Zoom会议还是自定义视频会话。
  2. 若用户需要真实的Zoom会议,则引导使用Meeting SDK。
  3. 引入相关的平台参考文档。
  4. 仅在会议创建、资源管理或报表场景下添加REST API。
  5. 仅当用例明确需要时,才添加webhooks或RTMS。

Primary References

主要参考文档

  • meeting-sdk
  • rest-api
  • webhooks
  • rtms
  • video-sdk
  • meeting-sdk
  • rest-api
  • webhooks
  • rtms
  • video-sdk

Common Mistakes

常见误区

  • Using Video SDK for normal Zoom meeting embeds
  • Mixing resource-management APIs into the core join flow without reason
  • Skipping platform-specific SDK constraints until too late
  • 为普通Zoom会议嵌入场景使用Video SDK
  • 无端将资源管理API混入核心入会流程
  • 过晚考虑平台特定的SDK限制