SDK Architecture and Workflow
1. API User Join/Start and Leave Meeting Sequence 2. Join/Start and Leave Meeting Sequence 3. Schedule, Edit, and Delete Meeting Sequence 4. SDK Footprint
The Zoom Windows SDK supports two options for user authentication:
You can pass a user ID to the SDK initialization - all meetings will start on that user’s account. This is referred to as the API user.
There are times where it might be cumbersome to get user ID when distributing your app to all Zoom users. In this case you could ask a user to input their Zoom login credentials into your app and then pass the SDK.
1. API User Join/Start and Leave Meeting Sequence:
2. Join/Start and Leave Meeting Sequence
Normal User :
3. Schedule, Edit, and Delete Meeting Sequence
4. SDK Footprint
The size of our Windows stack is about 18 MB. vcredist_x86.exe use 4 MB, and our core libs use about 9 MB.