Repository contains Base configuration and provides some examples for you to better understand the features of the Android Client SDK. The sample applications are meant to be used with the latest version of the Android Client SDK. Feel free to copy and modify the source code herein for your own projects. Please consider sharing your modifications with us, especially if they might benefit other developers using the OpenTok Android SDK.
Client allows to configure multiple settings during initialization:
- Basic client initialization (Kotlin, Java)
- Configure logging level (Kotlin, Java)
- Configure data center (Kotlin, Java)
- Configure server URL (Kotlin, Java)
These tasks are common for all communication channels:
- Login user (Kotlin, Java)
- Listen for client connection status changes (Kotlin, Java)
- Check if Client is connected (Kotlin, Java)
- Configure Firebase Messaging Service (Kotlin, Java)
Android Client SDK supports Messaging and Voice communication channels.
- Load conversation (Kotlin, Java)
- Create new conversation (Kotlin, Java)
- Load conversation events(Kotlin, Java)
- Load more conversation events, prev/next pages (Kotlin, Java)
- Send message (Kotlin, Java)
- Receive message (Kotlin, Java)
- Typing indicator (Kotlin, Java)
- Mark message as senn (Kotlin, Java)
- Mark message as delivered (Kotlin, Java)
- Invite user (Kotlin, Java)
- Join conversation (Kotlin, Java)
- Leave conversation (Kotlin, Java)
- Accept user invitation and join the conversation (Kotlin, Java)
- Member added to the conversation (Kotlin, Java)
- Member invited to the conversation (Kotlin, Java)
- Member removed from the conversation (Kotlin, Java)
- Send image attachment (Kotlin, Java)
- Receive image attachment (Kotlin, Java)
- Send custom event (Kotlin, Java)
- Receive custom event (Kotlin, Java)
- The event seen by another user (Kotlin, Java)
- Conversation has expired (Kotlin, Java)
- Documentation at API Developer Portal
- Tutorials at API Developer Portal
- Main interaction class: NexmoConversation
- Full code reference
The capabilities of in-app call
are limited, because they doesn't utilize Voice API. This method is recommended mostly for onboarding. Later, it is recommended to use a server managed call
.
- Start in-app call - (Kotlin, Java)
- Start server managed call (Kotlin, Java)
- Receive call events, DTMF (Kotlin, Java)
- Answer incoming call (Kotlin, Java)
- Hang up call (Kotlin, Java)
- Mute call / member / my member (Kotlin, Java)
- Unmute call / member / my member (Kotlin, Java)
- Enable Earmuff / member / my member (Kotlin, Java)
- Disable Earmuff / member / my member (Kotlin, Java)
- Documentation at API Developer Portal
- Tutorials at API Developer Portal
- Main interaction class: NexmoCall
- Full code reference