Developer Experience Guidelines - Android

This section provides best practices for creating a smooth and efficient development process when working with VideoSDK. From handling errors gracefully to managing resources and event subscriptions, these guidelines help developers build more reliable and maintainable applications. Following these practices can simplify troubleshooting, prevent common pitfalls, and improve overall application performance.

Initiate Key Features After Meeting Join Event

To provide a seamless and reliable meeting experience, initiate specific features only after the onMeetingJoined() event has been triggered.

• Trigger Key Actions After Joining the Meeting : Initiating crucial actions after the onMeetingJoined() event helps avoid errors and optimizes the meeting setup, ensuring a smoother experience for participants. If your application utilizes any of the following features or you want to perform any action as soon as meeting joins, it's recommended to call them only after the meeting has successfully started:

  • Chat Subscription: To enable in-meeting chat functionality, subscribe to the chat topic after the onMeetingJoined() event is triggered. This ensures that messages are reliably received by participants.

  • Device Management: If you need users to use specific audio or video devices when the meeting is first joined, you can utilize the setSelectedAudioDevice() and setSelectedVideoDevice() methods.

  • Recording and Transcription: To automatically start recording or transcription as soon as the meeting begins, configure the autoStartConfig in the createMeeting API. For detailed information, refer to the documentation here.

Dispose Custom Tracks When Necessary

Proper disposal of custom tracks is essential for managing system resources and ensuring a smooth experience. In most scenarios, tracks are automatically disposed of by the SDK, ensuring efficient resource management. However, in specific cases outlined below, you will need to dispose of custom tracks explicitly:

1. When Enabling/Disabling the Camera on a Precall Screen:

   • If your application includes a precall screen and you want to ensure that the device's camera is not used when the camera is disabled, you must dispose of the custom video track. Otherwise, the device’s camera will continue to be used even when the camera is off.
   • Additionally, remember to create a new track when the user enables the camera again.
   • If you don’t need to manage the camera's usage on the device level (i.e., you’re okay with the camera being used whether it’s enabled or disabled), you can skip this step.

2. When User Fails to Join the Meeting:

   • If a user is unable to join the meeting for any reason, it’s important to manually dispose custom tracks to avoid unnecessary resource consumption and ensure a clean state.The onMeetingStateChanged event will be triggered with FAILED or DISCONNECTED state if user is not able to join the meeting.

Listen for Error Events

Listening to error events enables your application to handle unexpected issues efficiently, providing users with clear feedback and potential solutions. Error codes pinpoint specific problems, whether from configuration settings, account restrictions, permission limitations, or device constraints. Here are recommended solutions based on common error categories:

1. Errors associated with Organization: If you encounter errors related to your organization (e.g., account status or participant limits), reach out to support at support@videosdk.live or message us on Discord for assistance.

2. Errors associated with Token: For errors related to authentication tokens, ensure the token is valid and hasn’t expired, then try the request again.

3. Errors associated with Meeting and Participant: Check that meetingId and participantId are correctly passed and valid. Also, ensure each participant has a unique participantId to avoid duplicate entries.

4. Errors associated with Add-on Service: If you encounter errors with add-on services (such as recording or streaming), try restarting the service after receiving a failure event. For example, if a START_RECORDING_FAILED error event occurs, attempt to call the startRecording() method again.

5. Errors associated with Media: Inform the user about media access issues, such as microphone or camera permissions. Design the UI to clearly indicate what is preventing the mic or camera from enabling, helping the user understand the problem.

6. Errors associated with Track: Ensure that the track you’ve created and passed to enable the mic or camera methods meets the required specifications.

7. Errors associated with Actions: If you need to perform actions as soon as a meeting joins, only initiate them after receiving the onMeetingJoined() event, otherwise it will not work well.