@tencent-rtc/mcp 1.4.6 → 1.6.0-beta.1

package/resource/knowledge/callkit/preset/web/api.md

@@ -0,0 +1,83 @@
+## TUICallKit (Includes UI Components)
+
+TUICallKit is an audio and video call component that **includes a UI component**. You can quickly implement a WhatsApp-like audio and video calling scenario with this component.
+
+|API|Description|
+|---------|---------|
+|[init](https://www.tencentcloud.com/document/product/647/51015#init)|Initialize TUICallKit.|
+|[calls](https://www.tencentcloud.com/document/product/647/51015#calls)|Initiate a one-to-one or multi-person call.|
+|[join](https://www.tencentcloud.com/document/product/647/51015#join)|Proactively join a call.|
+|[setCallingBell](https://www.tencentcloud.com/document/product/647/51015#setCallingBell)|Customize user's ringtone.|
+|[setSelfInfo](https://www.tencentcloud.com/document/product/647/51015#setSelfInfo)|Set your own nickname and avatar.|
+|[enableMuteMode](https://www.tencentcloud.com/document/product/647/51015#enableMuteMode)|Turn on/off ringtone.|
+|[enableFloatWindow](https://www.tencentcloud.com/document/product/647/51015#enableFloatWindow)|Turn on/off the floating window function.|
+|[enableVirtualBackground](https://www.tencentcloud.com/document/product/647/51015#enableVirtualBackground)|Turn on/off the blurred background function button.|
+|[setLanguage](https://www.tencentcloud.com/document/product/647/51015#setLanguage)|Set the call language for the TUICallKit component.|
+|[hideFeatureButton](https://www.tencentcloud.com/document/product/647/51015#hideFeatureButton)|Hidden Button.|
+|[setLocalViewBackgroundImage](https://www.tencentcloud.com/document/product/647/51015#setLocalViewBackgroundImage)|Set the background image for the local user's call interface.|
+|[setRemoteViewBackgroundImage](https://www.tencentcloud.com/document/product/647/51015#setRemoteViewBackgroundImage)|Set the background image for the remote user's call interface.|
+|[setLayoutMode](https://www.tencentcloud.com/document/product/647/51015#setLayoutMode)|Set the call interface layout mode.|
+|[setCameraDefaultState](https://www.tencentcloud.com/document/product/647/51015#setCameraDefaultState)|Set whether the camera is opened by default.|
+|[destroyed](https://www.tencentcloud.com/document/product/647/51015#destroyed)|Destroy TUICallKit.|
+|[getTUICallEngineInstance](https://www.tencentcloud.com/document/product/647/51015#getTUICallEngineInstance)|Get TUICallEngine instance.|
+
+## TUICallEngine (No UI)
+
+TUICallEngine API is an audio and video call component that **offers a No UI interface**. You can use this set of APIs to custom encapsulate according to your business needs.
+
+|API|Description|
+|---------|---------|
+|[createInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#.createInstance)|Creating a TUICallEngine Instance (Singleton Pattern)|
+|[destroyInstance](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#destroyInstance)|Terminating a TUICallEngine Instance (Singleton Pattern)|
+|[on](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#on)|Listening on events|
+|[off](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#off)|Canceling Event Listening|
+|[login](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#login)|Sign in Interface|
+|[logout](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#logout)|Logout Interface|
+|[setSelfInfo](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setSelfInfo)|Configure the user's nickname and profile photo|
+|[calls](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#calls)|Initiate a one-on-one call|
+|[join](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#join)|Proactively join a call.|
+|[accept](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#accept)|Answer Calls|
+|[reject](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#reject)|Decline Call|
+|[hangup](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#hangup)|End Calls|
+|[startRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#startRemoteView)|Initiate Remote Screen Rendering|
+|[stopRemoteView](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#stopRemoteView)|Stop Remote Screen Rendering|
+|[openCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openCamera)|Enable the camera|
+|[closeCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeCamera)|Turn Off Camera|
+|[switchCamera](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchCamera)|Switch between front and rear cameras, note: only supported on mobile devices.|
+|[openMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#openMicrophone)|Enable Microphone|
+|[closeMicrophone](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#closeMicrophone)|Turn off the microphone|
+|[setVideoQuality](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVideoQuality)|Set video quality|
+|[getDeviceList](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#getDeviceList)|Access device list|
+|[switchDevice](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#switchDevice)|Switch camera or microphone devices|
+|[enableMultiDeviceAbility](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#enableMultiDeviceAbility)|Turn on/off the multi-device login mode of TUICallEngine.|
+|[setBlurBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setBlurBackground)|Switch/set background blur|
+|[setVirtualBackground](https://web.sdk.qcloud.com/component/trtccalling/doc/TUICallEngine/web/en/TUICallEngine.html#setVirtualBackground)|Switch/set image background blur|
+
+## Event Types
+
+TUICallEvent is the callback event class corresponding to TUICallEngine. Through this callback, you can listen to the callback events of interest.
+
+|EVENT|Description|
+|---------|---------|
+|[TUICallEvent.ERROR](https://www.tencentcloud.com/document/product/647/51017#error)|An error occurred during the call.|
+|[TUICallEvent.KICKED_OUT](https://www.tencentcloud.com/document/product/647/51017#kicked_out)|Receiving this event after a duplicate sign-in indicates that the user has been removed from the room|
+|[TUICallEvent.USER_ACCEPT](https://www.tencentcloud.com/document/product/647/51017#user_accept)|If a user answers, this event will be received.** v4.x.x is deprecated**|
+|[TUICallEvent.USER_ENTER](https://www.tencentcloud.com/document/product/647/51017#user_enter)|A user joined the call.|
+|[TUICallEvent.USER_LEAVE](https://www.tencentcloud.com/document/product/647/51017#user_leave)|A user left the call.|
+|[TUICallEvent.REJECT](https://www.tencentcloud.com/document/product/647/51017#reject)|A user declined the call.|
+|[TUICallEvent.NO_RESP](https://www.tencentcloud.com/document/product/647/51017#no_resp)|A user didn't respond.|
+|[TUICallEvent.LINE_BUSY](https://www.tencentcloud.com/document/product/647/51017#line_busy)|A user was busy.|
+|[TUICallEvent.USER_VIDEO_AVAILABLE](https://www.tencentcloud.com/document/product/647/51017#user_video_available)|Whether a user has a video stream.|
+|[TUICallEvent.USER_AUDIO_AVAILABLE](https://www.tencentcloud.com/document/product/647/51017#user_audio_available)|Whether a user has an audio stream.|
+|[TUICallEvent.USER_VOICE_VOLUME](https://www.tencentcloud.com/document/product/647/51017#user_voice_volume)|The volume levels of all users.|
+|TUICallEvent.ON_CALL_BEGIN|Call connected event|
+|TUICallEvent.ON_CALL_RECEIVED|Call request event|
+|TUICallEvent.ON_CALL_CONNECTED|Call not connected event|
+|TUICallEvent.ON_CALL_END|The call ended.|
+|[TUICallEvent.DEVICED_UPDATED](https://www.tencentcloud.com/document/product/647/51017#deviced_updated)|Device list update, this event will be received|
+|TUICallEvent.ON_USER_NETWORK_QUALITY_CHANGED|All user network quality events|
+
+## Document Link
+- [TUICallEngine](https://www.tencentcloud.com/document/product/647/51016)
+
+- [TUICallEvent](https://www.tencentcloud.com/document/product/647/51017)

package/resource/knowledge/chat/preset/android/features/chat-setting.md

@@ -0,0 +1,74 @@
+## Component Overview
+
+ChatSetting is a set of chat settings components built with Jetpack Compose. It includes two main components: C2CChatSetting (C2C Chat Settings) and GroupChatSetting (Group Chat Settings).
+
+These components offer comprehensive chat session management features, such as user information management, permission controls, group management, and other essential capabilities.
+| <strong>C2C Chat Settings Interface</strong> | <strong>Group Chat Settings Interface</strong> |
+| --- | --- |
+|  |  |
+
+## Component Integration
+
+The ChatSetting component is included in TUIKit Compose. To use ChatSetting, integrate TUIKit Compose into your project. For detailed integration steps, see the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459).
+
+## Component Structure
+
+ChatSetting consists of two main components: C2CChatSetting (C2C Chat Settings) and GroupChatSetting (Group Chat Settings). Each component offers a variety of configuration options.
+
+### C2C Chat Settings (C2CChatSetting)
+
+#### Public Methods
+| Method | Parameter | Description |
+| --- | --- | --- |
+| <code>C2CChatSetting</code> | <code>userID: String</code> | The user ID of the other participant. Used to identify the chat target. |
+| <code>modifier: Modifier</code> | Jetpack Compose modifier for setting the component's style, layout, behavior, and appearance. |  |
+| <code>onSendMessageClick: () -> Unit</code> | Webhook triggered when the Send Message button is clicked. Optional parameter. |  |
+| <code>onContactDelete: () -> Unit</code> | Webhook triggered when the Delete Contact button is clicked. Optional parameter. |  |
+| <code>c2cChatSettingViewModelFactory: C2CChatSettingViewModelFactory</code> | Factory for creating the internal C2CChatSettingViewModel. Typically, you do not need to provide this manually, as the component supplies a default implementation. |  |
+
+### Group Chat Settings (GroupChatSetting)
+
+#### Public Methods
+| Method | Parameter | Description |
+| --- | --- | --- |
+| <code>GroupChatSetting</code> | <code>groupID: String</code> | Group ID. Used to identify the group chat. |
+| <code>modifier: Modifier</code> | Jetpack Compose modifier for setting the component's style, layout, behavior, and appearance. |  |
+| <code>onSendMessageClick: () -> Unit</code> | Webhook triggered when the Send Message button is clicked. Optional parameter. |  |
+| <code>onGroupMemberClick: (GroupMember) -> Unit </code> | Webhook triggered when a group member is clicked. Optional parameter. |  |
+| <code>onGroupDelete: () -> Unit</code> | Webhook triggered when the Dissolve/Leave Group button is clicked. Optional parameter. |  |
+| <code>groupChatSettingViewModelFactory: GroupChatSettingViewModelFactory</code> | Factory for creating the internal GroupChatSettingViewModel. Typically, you do not need to provide this manually, as the component supplies a default implementation. |  |
+
+## Basic Usage
+
+To display the C2C Chat Settings page, initialize C2CChatSetting as shown below:
+``` swift
+Box {
+    C2CChatSetting(
+        userID = userID,
+        onSendMessageClick = {
+            // Handle send message click event
+        },
+        onContactDelete = {
+            // Handle contact delete click event
+        },
+    )
+}
+```
+
+To display the Group Chat Settings page, initialize GroupChatSetting as shown below:
+``` swift
+Box {
+    GroupChatSetting(
+        groupID = groupID,
+        onGroupMemberClick = { groupMember ->
+            // Handle group member click event
+        },
+        onSendMessageClick = {
+            // Handle send message click event
+        },
+        onGroupDelete = {
+            // Handle dissolve/leave group event
+        },
+    )
+}
+```

package/resource/knowledge/chat/preset/android/features/contact-list.md

@@ -0,0 +1,43 @@
+## Component Overview
+
+ContactList is a Jetpack Compose-based contact list component that provides users with robust contact management features. It supports displaying friends, handling friend requests, managing group lists, managing blacklists, and offers a comprehensive set of interactive webhook interfaces.
+| <strong>Contact List</strong> | <strong>Group List</strong> | <strong>Friend Request List</strong> |
+| --- | --- | --- |
+|  |  |  |
+
+## Component Integration
+
+The `ContactList` component is included in TUIKit Compose. To use `ContactList`, integrate TUIKit Compose into your project. For detailed integration steps, see the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459).
+
+## Component Structure
+
+`ContactList` is the primary component for displaying the contact list page:
+| <strong>Method</strong> | <strong>Parameter</strong> | <strong>Description</strong> |
+| --- | --- | --- |
+| <code>ContactList</code> | <code>modifier: Modifier</code> | Jetpack Compose modifier for configuring the component’s style, layout, behavior, and appearance. |
+| <code>onGroupClick: (ContactInfo) -> Unit</code> | Webhook triggered when a group is clicked; this parameter is optional. |  |
+| <code>onContactClick: (ContactInfo) -> Unit</code> | Webhook triggered when a contact is clicked; this parameter is optional. |  |
+| <code>contactListViewModelFactory: ContactListViewModelFactory</code> | Factory for creating the internal ContactListViewModel. Typically, you do not need to provide this manually, as a default implementation is included. |  |
+
+The top section of `ContactList` provides entry points for subviews such as friend requests, group chat requests, group chat list, and blacklist. The bottom section displays the contact list, as shown below:
+
+## Basic Usage
+- When you tap the entry points for friend requests, group chat requests, group chat list, or blacklist in `ContactList`, the component automatically handles navigation—no extra configuration is required.
+
+- When you tap a group in the group chat list or a contact in the contact list or blacklist, the corresponding webhook (`onGroupClick` or `onContactClick`) is triggered. You must handle these webhooks to implement custom navigation. See the routing example below:
+
+   To display the contact list directly, initialize `ContactList` as shown below:
+
+   ``` swift
+   Box(
+       modifier = Modifier
+           .fillMaxSize()
+           .systemBarsPadding()
+   ) {
+       ContactList(onGroupClick = {
+           // Handle group click event
+       }, onContactClick = {
+           // Handle contact click event
+       })
+   }
+   ```

package/resource/knowledge/chat/preset/android/features/conversation-list.md

@@ -0,0 +1,117 @@
+## Component Overview
+
+ConversationList is a Jetpack Compose component designed to display and manage user chat conversations. It offers a comprehensive set of features for viewing and interacting with conversations.
+| <strong>Conversation List</strong> | <strong>Conversation Actions</strong> |
+| --- | --- |
+|  |  |
+
+## Component Integration
+
+ConversationList is part of TUIKit Compose. To use ConversationList, integrate TUIKit Compose into your project. For detailed integration steps, see the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459).
+
+## Component Structure
+
+ConversationList exposes only its initialization method; all other logic is handled internally.
+
+#### Public Methods
+| Method | Parameter | Description |
+| --- | --- | --- |
+| <code>ConversationList</code> | <code>modifier: Modifier</code> | Sets the component's style, layout, behavior, and appearance in Jetpack Compose. |
+| <code>conversationListViewModelFactory: ConversationListViewModelFactory</code> | Factory for creating the internal ConversationListViewModel. Typically, you do not need to provide this manually, as a default implementation is included. |  |
+| <code>config: ConversationActionConfigProtocol</code> | Initializes the component and sets conversation action menu items. Optional. |  |
+| <code>customActions: List</code> | Initializes the component and sets custom conversation action options. Optional. |  |
+| <code>onConversationClick: (ConversationInfo) -> Unit</code> | Sets the conversation click webhook. |  |
+
+## Basic Usage
+
+Initialize the ConversationList component directly. The onConversationClick webhook is required.
+
+|Parameter Name|Type|Description|
+|---------|---------|---------|
+|`onConversationClick`|`(ConversationInfo) -> Unit`|Conversation click webhook, triggered when a user taps a conversation cell.|
+
+Example code:
+``` swift
+Box(
+    modifier = Modifier
+        .fillMaxSize()
+        .systemBarsPadding()
+) {
+    ConversationList(onConversationClick = {
+        // Recommended: Navigate to the chat page here
+    })
+}
+```
+
+## Customization
+
+You can customize the conversation list action items as follows.
+
+#### Method 1. Hide Conversation Action Items Locally
+
+Set `actions` when initializing ConversationList to specify which action items appear in each conversation cell:
+``` swift
+Box {
+    ConversationList(
+        // Hide ClearHistory
+        config = ChatConversationActionConfig(
+            isSupportDelete = true,
+            isSupportPin = true,
+            isSupportClearHistory = false
+        )
+    ) {
+        // Navigate on conversation cell click
+    }
+}
+```
+
+**Supported Action Menu Toggles**
+
+|Action Type|Description|
+|---------|---------|
+|`isSupportDelete`|Enable or disable deleting conversations.|
+|`isSupportPin`|Enable or disable pinning conversations.|
+|`isSupportClearHistory`|Enable or disable clearing conversation history.|
+
+#### Method 2. Add Conversation Action Items Locally
+
+Pass `customActions` when initializing ConversationList. Custom options will be added to the end of the default action menu:
+
+|Parameter Name|Type|Description|
+|---------|---------|---------|
+|`customActions`|`List`|Custom conversation actions, shown when the user opens the conversation action menu.|
+
+Example code:
+``` swift
+Box {
+    ConversationList(
+        customActions = listOf(ConversationCustomAction(title = "Share") {
+            println("Share conversation: ${it.title}")
+        })
+    ) {
+        // Handle click events
+    }
+}
+```
+
+#### Method 3. Global Configuration
+
+Configure globally using `AppBuilderConfig`:
+``` swift
+// Set up at app startup; if omitted, the feature is disabled
+AppBuilderConfig.conversationActionList = listOf(
+    ConversationAction.DELETE,           // Enable delete
+    ConversationAction.PIN,              // Enable pin
+    ConversationAction.CLEAR_HISTORY     // Enable clear conversation messages
+)
+
+// Then, initialize ConversationList. All ConversationList instances will use the above conversationActionList configuration.
+ConversationList() {
+    // Navigate to the chat page here if needed
+}
+```
+
+The following images show the customization effects:
+| <strong>Conversation Actions</strong><br><strong> (Default Options)</strong> | <strong>Conversation Actions</strong><br><strong> (Delete Option Hidden)</strong> | <strong>Conversation Actions </strong><br><strong>(Share Option Added)</strong> |
+| --- | --- | --- |
+|  |  |  |

package/resource/knowledge/chat/preset/android/features/language.md

@@ -0,0 +1,136 @@
+## Feature Description
+
+`TUIKit Compose` includes built-in language packs for **English**, **Simplified Chinese**, **Traditional Chinese**, and **Arabic** as default interface languages.
+
+You can use these default language packs, customize translation strings, or add additional language packs as needed.
+
+|**English**|**Arabic**|**Simplified Chinese**|
+|---------|---------|---------|
+||||
+
+## Using Built-in Languages
+
+If your application only needs to support **English**, **Simplified Chinese**, **Traditional Chinese**, or **Arabic**, follow the instructions in this section.
+
+### Following System Language
+
+By default, `TUIKit Compose` automatically adapts to the system language without additional configuration. If the system language is not one of the four supported languages, the interface defaults to English.
+
+### Setting a Specific Display Language
+
+To manually specify the interface language for `TUIKit Compose`, use `setApplicationLocales` to set the desired language. Once specified, the component will not follow the system language. Example:
+``` swift
+// Supported languages:
+// "zh" for Simplified Chinese
+// "zh-hk" for Traditional Chinese
+// "en" for English
+// "ar" for Arabic
+AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("zh"))
+```
+
+> **Notice：**
+>
+
+> The `setApplicationLocales` method requires a dependency on androidx.appcompat:appcompat, version 1.6.0 or higher.
+>
+
+## Using Additional Languages or Custom Translations
+
+If your application needs to support more languages or modify specific translation strings, follow the steps in this section.
+
+This example demonstrates how to add a Korean language pack and customize translations.
+
+### Adding Language Resource Files
+
+Create a `values-ko` directory and the corresponding string resource files under the `res` directory for each module. `ko` is the language code for Korean, following Android resource qualifier conventions. After adding Korean, your project structure will look like this:
+``` plaintext
+chat/demo/app/src/main/res/
+├── values/strings.xml
+├── values-zh/strings.xml
+├── values-zh-rHK/strings.xml
+├── values-ar/strings.xml
+└── values-ko/strings.xml
+
+chat/uikit/src/main/res/
+├── values/strings.xml
+├── values-zh/strings.xml
+├── values-zh-rHK/strings.xml
+├── values-ar/strings.xml
+└── values-ko/strings.xml
+
+atomic-x/src/main/
+├── res-album-picker/values-ko/strings.xml
+├── res-base-component/values-ko/strings.xml
+├── res-chat-setting/values-ko/strings.xml
+├── res-contact-list/values-ko/strings.xml
+├── res-conversation-list/values-ko/strings.xml
+├── res-emoji-picker/values-ko/strings.xml
+├── res-emoji-picker/values-ko/strings-emoji.xml
+├── res-message-input/values-ko/strings.xml
+├── res-message-list/values-ko/strings.xml
+├── res-search/values-ko/strings.xml
+└── res-video-recorder/values-ko/strings.xml
+```
+
+Use the default `strings.xml` file in each module as a reference and translate each `key` into Korean.
+
+> **Note：**
+>
+> 1. Multilingual resources for `TUIKit Compose` are distributed across multiple modules: `app`, `uikit`, and `atomic-x`. Add `values-ko` to all relevant modules.
+> 2. The `res-emoji-picker` module includes both `strings.xml` and `strings-emoji.xml`. When adding a new language, complete both files.
+> 3. For language codes, see Resource Qualifier Rules.
+
+### Customizing Translation Strings
+
+After adding the Korean resource file (`values-ko/strings.xml`), the string `key`s remain consistent across language files. Customize translation content as needed for your business. To update specific text, override the relevant entry in the target module; you do not need to modify other language files.
+
+### Following System Language
+
+Android automatically matches the resource directory based on the system language. For example, if the system language is Korean, it will load resources from `values-ko`.
+
+The newly added resource directory must follow Android resource qualifier rules to ensure the component adapts to the system language.
+
+If you previously set a specific language using `setApplicationLocales`, clear the setting to revert to system language adaptation:
+``` swift
+AppCompatDelegate.setApplicationLocales(LocaleListCompat.getEmptyLocaleList())
+```
+
+### Setting a Specific Display Language
+
+To set the interface language of `TUIKit Compose` to Korean, use `setApplicationLocales` with the Korean language code. Once set, the component will not follow the system language. Example:
+``` swift
+// Supported languages:
+// "zh" for Simplified Chinese
+// "zh-hk" for Traditional Chinese
+// "en" for English
+// "ar" for Arabic
+// "ko" for Korean
+AppCompatDelegate.setApplicationLocales(LocaleListCompat.forLanguageTags("ko"))
+```
+
+Once these steps are complete, the interface displays in Korean, as shown below:
+
+## Appendix: Resource Qualifier Rules
+
+|Language|Code|Language|Code|
+|---------|---------|---------|---------|
+|Arabic|ar|Bulgarian|bg|
+|Croatian|hr|Czech|cs|
+|Danish|da|German|de|
+|Greek|el|English|en|
+|Estonian|et|Spanish|es|
+|Finnish|fi|French|fr|
+|Irish|ga|Hindi|hi|
+|Hungarian|hu|Hebrew|he|
+|Italian|it|Japanese|ja|
+|Korean|ko|Latvian|lv|
+|Lithuanian|lt|Dutch|nl|
+|Norwegian|no|Polish|pl|
+|Portuguese|pt|Swedish|sv|
+|Romanian|ro|Russian|ru|
+|Serbian|sr|Slovak|sk|
+|Slovenian|sl|Thai|th|
+|Turkish|tr|Ukrainian|uk|
+|Chinese (Simplified)|zh|Chinese (Traditional)|zh-rHK|
+
+For the full list, [see here](https://quickref.me/iso-639-1).

package/resource/knowledge/chat/preset/android/features/message-input.md

@@ -0,0 +1,57 @@
+## Component Overview
+
+MessageInput is a Jetpack Compose component that provides a full-featured message input interface for users. It supports composing and sending various message types, including text, images, videos, files, and voice messages. Additional features include emoji selection, flexible style configuration, and extensive customization options.
+| <strong>Message Input Interface</strong> | <strong>Emoji Picker</strong> |
+| --- | --- |
+|  |  |
+
+## Component Integration
+
+MessageInput is included in TUIKit Compose. To use MessageInput, integrate TUIKit Compose into your project. For detailed integration steps, see the [TUIKit Compose](https://www.tencentcloud.com/document/product/1047/77459) documentation.
+
+## Component Structure
+
+MessageInput consists of the main input component and a style configuration protocol, enabling message input functionality with support for customization.
+
+#### Public Methods
+| Method | Parameter | Description |
+| --- | --- | --- |
+| <code> MessageInput</code> | <code>conversationID: String</code> | Conversation ID that identifies the current chat session.<br>- For C2C Chat, use the format c2c_userID.<br>- For group chat, use group_groupID. |
+| <code>modifier: Modifier</code> | Jetpack Compose modifier for configuring style, layout, behavior, and appearance. |  |
+| <code>config: MessageInputConfigProtocol</code> | Input style configuration that controls which function buttons are displayed. |  |
+| <code>messageInputViewModelFactory: MessageInputViewModelFactory</code> | Factory for creating the internal MessageInputViewModel. Typically, you do not need to provide this manually, as a default implementation is available. |  |
+
+## Basic Usage
+
+Initialize and use the MessageInput component by passing a conversation ID.
+``` swift
+Box(
+    modifier = Modifier
+        .fillMaxWidth()
+) {
+    MessageInput(
+        conversationID = conversationID,
+        modifier = Modifier.navigationBarsPadding()
+    )
+}
+```
+
+## Customization
+
+Customize which feature buttons appear on the input bar:
+``` swift
+// Specify which function buttons to display
+MessageInput(
+    conversationID = conversationID,
+    config = ChatMessageInputConfig(
+        isShowAudioRecorder = false,   // Hide audio recording
+        isShowPhotoTaker = true,       // Show photo capture
+        isShowMore = true,             // Show more features
+    )
+)
+```
+
+See the customization results below:
+| <strong>Default Input Box</strong> | <strong>Audio Recording Hidden</strong> | <strong>All Features Hidden</strong> |
+| --- | --- | --- |
+|  |  |  |

package/resource/knowledge/chat/preset/android/features/message-list.md

@@ -0,0 +1,142 @@
+## Component Overview
+
+MessageList is a Jetpack Compose component designed to display and manage chat messages. It provides robust support for various message types and operations:
+- Supported message types: text, image, video, audio, file, system notification, emoji, and more.
+
+- Message actions: supports long-press menus for actions such as copy, delete, recall, and custom options.
+
+- Highly customizable: configure styles (bubble color, corner radius, font, etc.) and custom action items.
+
+| <strong>Chat Message List</strong> | <strong>Message Long-Press Menu</strong> |
+| --- | --- |
+|  |  |
+
+## Component Integration
+
+MessageList is part of TUIKit Compose. To use MessageList, integrate TUIKit Compose into your project. For integration instructions, see the [TUIKit Compose documentation](https://www.tencentcloud.com/document/product/1047/77459).
+
+## Component Structure
+
+MessageList exposes only its initialization method; all other logic is handled internally.
+
+#### Public Methods
+| Method | Parameter | Description |
+| --- | --- | --- |
+| <code>MessageList</code> | <code>conversationID: String</code> | Initializes the component and sets the conversation ID.<br>- For C2C Chat, use the format c2c_userID.<br>- For group chat, use group_groupID. |
+| <code>modifier: Modifier </code> | Jetpack Compose modifier for setting style, layout, behavior, and appearance. |  |
+| <code>config: MessageListConfigProtocol</code> | Initializes the component and applies message list styles. |  |
+| <code>customActions: List</code> | Initializes the component and adds custom message menu actions. |  |
+| <code>locateMessage: MessageInfo?</code> | Initializes the component and sets the message to locate. Typically used to jump from message search results to the target message. |  |
+| <code>messageListViewModelFactory: MessageListViewModelFactory</code> | Factory for creating the internal MessageListViewModel. Usually, you do not need to provide this, as a default implementation is included. |  |
+| <code>onUserClick: (String) -> Unit</code> | Initializes the component and sets the handler for user avatar clicks. |  |
+
+## Basic Usage
+
+You can initialize the MessageList component directly by providing a conversation ID. It is also recommended to implement the onUserClick handler during initialization.
+``` swift
+Box(modifier = Modifier.systemBarsPadding()) {
+    MessageList(conversationID = conversationID) {
+        // Handle user avatar click event
+    }
+}
+```
+
+## Customization
+
+You can customize both the style and action items of the message list as needed.
+
+#### Custom Styles
+
+Implement `MessageListConfigProtocol` to define a fully customized style:
+``` swift
+class MyCustomConfig(
+    override val alignment: MessageAlignment = MessageAlignment.TWO_SIDED,
+    override val isShowTimeMessage: Boolean = true,
+    override val isShowLeftAvatar: Boolean = true,
+    override val isShowLeftNickname: Boolean = true,
+    override val isShowRightAvatar: Boolean = true,
+    override val isShowRightNickname: Boolean = true,
+    // ... other required properties
+) : MessageListConfigProtocol
+
+MessageList(conversationID = conversationID, config = MyCustomConfig()) {
+    // Handle user avatar click event
+}
+```
+
+`MessageListConfigProtocol` Property Descriptions:
+| Property | Type | Description | Remarks |
+| --- | --- | --- | --- |
+| <code>alignment</code> | <code>MessageAlignment</code> | Message alignment | - <code>MessageAlignment.LEFT</code>: left aligned. - <code>MessageAlignment.RIGHT</code>: right aligned. - <code>MessageAlignment.TWO_SIDED</code>: both sides aligned. |
+| <code>isShowTimeMessage</code> | <code>Boolean</code> | Show message timestamps | Controls whether message timestamps are displayed. |
+| <code>isShowLeftAvatar</code> | <code>Boolean</code> | Show left avatar | Controls whether the sender's avatar is shown for received messages. |
+| <code>isShowLeftNickname</code> | <code>Boolean</code> | Show left nickname | Controls whether the sender's nickname is shown for received messages. |
+| <code>isShowRightAvatar</code> | <code>Boolean</code> | Show right avatar | Controls whether your avatar is shown for sent messages. |
+| <code>isShowRightNickname</code> | <code>Boolean</code> | Show right nickname | Controls whether your nickname is shown for sent messages. |
+| <code>isShowTimeInBubble</code> | <code>Boolean</code> | Show time inside bubble | Controls whether the timestamp appears inside the message bubble. |
+| <code>cellSpacing</code> | <code>Dp</code> | Message spacing | Controls the spacing between adjacent messages. |
+| <code>isShowSystemMessage</code> | <code>Boolean</code> | Show system notifications | Controls whether system notification messages are displayed. |
+| <code>isShowUnsupportMessage</code> | <code>Boolean</code> | Show unsupported messages | Controls whether unsupported message types are displayed. |
+| <code>horizontalPadding</code> | <code>Dp</code> | Horizontal padding | Controls the left and right padding of the message list. |
+| <code>avatarSpacing</code> | <code>Dp</code> | Avatar spacing | Controls the spacing between the avatar and message content. |
+| <code>isSupportCopy</code> | <code>Boolean</code> | Enable copy in message menu | - <code>true</code>: Display the copy action.<br>- <code>false</code>: Do not display the copy action. |
+| <code>isSupportDelete</code> | <code>Boolean</code> | Enable delete in message menu | - <code>true</code>: Display the delete action.<br>- <code>false</code>: Do not display the delete action. |
+| <code>isSupportRecall</code> | <code>Boolean</code> | Enable recall in message menu | - <code>true</code>: Display the recall action.<br>- <code>false</code>: Do not display the recall action. |
+
+### Custom Action Items
+
+You can customize the long-press message menu in several ways.
+
+#### Method 1. Show or Hide Action Items Locally
+
+Set `isSupportCopy`, `isSupportDelete`, and `isSupportRecall` in the config parameter when initializing MessageList to control which actions are available:
+``` swift
+MessageList(
+    conversationID = conversationID,
+    config = ChatMessageListConfig(isSupportCopy = false)
+) {
+    // Handle user avatar click event
+}
+```
+
+#### Method 2. Add Custom Action Items Locally
+
+Pass a list of custom actions to the `customActions` parameter when initializing MessageList. Your custom actions will appear below the default actions:
+``` swift
+MessageList(
+    conversationID = conversationID,
+    customActions = listOf(
+        MessageCustomAction(title = "Share", iconResID = R.drawable.message_list_menu_forward_icon) {
+            println("Share Message")
+        }
+    )
+)
+```
+
+#### Method 3. Configure Action Items Globally
+
+Set global action items using `AppBuilderConfig`:
+``` swift
+// Configure at app startup
+AppBuilderConfig.messageActionList = listOf(
+    MessageAction.COPY,    // Enable copy
+    MessageAction.DELETE,  // Enable delete
+    MessageAction.RECALL   // Enable recall
+)
+
+// Then initialize MessageList; all instances will use the above configuration
+MessageList(
+    conversationID = conversationID,
+)
+```
+
+> **Note：**
+>
+
+> Local configuration takes precedence over global configuration.
+>
+
+Customization examples:
+| <strong>Message List Actions</strong><br><strong> (Default Options)</strong> | <strong>Message List Actions</strong><br><strong> (Copy Option Hidden)</strong> | <strong>Message List Actions </strong><br><strong>(Share Option Added)</strong> |
+| --- | --- | --- |
+|  |  |  |