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

package/resource/{doc → knowledge}/livekit/core-sdk/live/flutter/live-integration.md

@@ -2,31 +2,31 @@ This documentation guides you through using the core component of the AtomicXCor
 
 ## Core Features
 
-**LiveCoreWidget** is a lightweight widget purpose-built for live streaming scenarios and serves as the foundation of your live streaming interface. It abstracts complex live streaming technologies—including streaming, co-hosting, and audio/video rendering—so you can use LiveCoreWidget as the canvas for your live video. This allows you to focus on developing your custom UI and interactive features.
+**LiveCoreWidget** is a lightweight widget built for live streaming scenarios. As the foundation of your live streaming implementation, it abstracts away the complexities of streaming, co-hosting, and audio and video rendering. Use LiveCoreWidget as the video canvas for your live stream, so you can focus on building your UI and interactive features.
 
-The following diagram illustrates where **LiveCoreWidget** fits within your live streaming interface and its role in the view hierarchy:
+The image below shows how LiveCoreWidget fits into the live streaming interface:
 
 ## Preparations
 
 ### Step 1: Activate the Service
 
-See Activate Service to obtain either the trial or paid version of the SDK.Then, go to [the Console](https://console.trtc.io/app) for application management, and get the following:
-- `SDKAppID`: Application identifier (required). Tencent Cloud uses `SDKAppID` for billing and details.
+See Activate the Service to obtain either the trial or paid version of the SDK. Then, go to [the Console](https://console.trtc.io/app) for application management, and get the following:
+- `SDKAppID`: Application identifier (required). TRTC uses `SDKAppID` for billing and details.
 
-- `SDKSecretKey`: Application secret key, used to initialize the configuration file with secret information.
+- `SDKSecretKey`: Application secret key.
 
 ### Step 2: Import AtomicXCore into Your Project
-1. **Component installation**: Please add the `atomic_x_core` dependency in your `pubspec.yaml` file and execute `flutter pub get`.
+1. **Install the SDK**: Add the `atomic_x_core` dependency in your `pubspec.yaml` file and execute `flutter pub get`.
 
    ``` yaml
    dependencies:
-     atomic_x_core: ^3.6.0
+     atomic_x_core: ^4.0.1
    ```
 2. **Configure project permissions:** Both Android and iOS projects require configuration.
 
 【Android】
 
-Please add permission to use camera and microphone in the `android/app/src/main/AndroidManifest.xml` file.
+Add camera and microphone permissions to your `android/app/src/main/AndroidManifest.xml` file.
 ``` xml
 <uses-permission android:name="android.permission.CAMERA" />
 <uses-permission android:name="android.permission.RECORD_AUDIO" />
@@ -34,9 +34,9 @@ Please add permission to use camera and microphone in the `android/app/src/main/
 
 【iOS】
 
-Please add permission to use camera and microphone in the `iOS` directory **Podfile** and `ios/Runner` directory `Info.plist` file.
+Add camera and microphone usage descriptions to your app’s **Podfile** in the `iOS` directory and to the `Info.plist` file in the `ios/Runner` directory.
 
-**Podfile**
+**Podfile:**
 ``` ruby
 post_install do |installer|
   installer.pods_project.targets.each do |target|
@@ -52,7 +52,7 @@ post_install do |installer|
 end
 ```
 
-**Info.plist**
+**Info.plist:**
 ``` xml
 <key>NSCameraUsageDescription</key>
 <string>TUILiveKit needs to access your camera permission. Video recording with picture only after enabling.</string>
@@ -62,12 +62,12 @@ end
 
 ### Step 3: Implement Login Logic
 
-Call `LoginStore.shared.login` in your project to complete login. **This is the key premise for using all functions of AtomicXCore.**
+Call `LoginStore.shared.login` in your project to log in. **This is the key premise for using all functions of AtomicXCore.**
 
 > **Important:**
 >
 
-> It is recommended to call LoginStore.shared.login after successful log-in to your App's user account to ensure clear and consistent business logic.
+> It is recommended to call `LoginStore.shared.login` after successful log-in to your App's user account to ensure clear and consistent business logic.
 >
 
 ``` java
@@ -93,28 +93,28 @@ void main() async {
 }
 ```
 
-**Logon API parameter description:**
-| **Parameter** | **Type** | **Note** |
+**Login API parameters:**
+| <strong>Parameter</strong> | <strong>Type</strong> | <strong>Note</strong> |
 | --- | --- | --- |
-| `sdkAppID` | `int` | Get this from [TRTC console](https://console.trtc.io/app). |
-| `userID` | `String` | The unique ID for the current user. Must contain only English letters, numbers, hyphens, and underscores.. To avoid multi-end login conflict, **do not use**`1`, `123`**or other simple IDs**. |
-| `userSig` | `String` | A ticket for Tencent Cloud authentication. Please note:<br>- Development Environment: You can use the local `GenerateTestUserSig.genTestSig` function to generate a `UserSig` or generate a temporary UserSig via the [UserSig Generation Tool](https://console.trtc.io/usersig).<br>- Production Environment: To prevent key leakage, you must use a server-side method to generate `UserSig`. For details, see Generating UserSig on the Server. |
+| <code>sdkAppID</code> | <code>int</code> | Your application identifier, which can be obtained from <a href="https://console.trtc.io/app">TRTC console</a>. |
+| <code>userID</code> | <code>String</code> | - The unique ID for the current user.<br>- Only letters, numbers, hyphens, and underscores are allowed.<br>- To avoid login conflicts across devices, do not use simple IDs like 1, 123, etc. |
+| <code>userSig</code> | <code>String</code> | Credential for TRTC authentication. Please note:<br>- In development environment: You can use the local <code>GenerateTestUserSig.genTestSig</code> function to generate a <code>UserSig</code> or generate a temporary UserSig via the <a href="https://console.trtc.io/usersig">UserSig Generation Tool</a>.<br>- In production environment: To prevent SecretKey leakage, always generate <code>UserSig</code> on your server. For details, see Generating UserSig on the Server. |
 
 ## Building a Basic Live Room
 
-### Step 1: Implement Broadcaster Video Streaming
+### Step 1: Host Video Streaming Setup
 
-The anchor starts live streaming process is as follows. You just need to perform the following steps to quickly build a live stream.
+Follow these steps to quickly set up host video streaming:
 
 > **Note:**
 >
 
-> For the business code of live stream publishing, you can also refer to the [live_room_anchor_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/live_room_anchor_widget.dart) file in the TUILiveKit open-source project to understand the complete implementation logic.
+> For a complete host streaming implementation, see [live_room_anchor_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/live_room_anchor_widget.dart) in the TUILiveKit open-source project.
 >
 
-1. **Initialize the Anchor live streaming view**
+1. **Initialize Host Streaming View**
 
-   On your Anchor page, create a `LiveCoreWidget` instance and control the live stream behavior through `LiveCoreController`.
+   On your host page, create a `LiveCoreWidget` instance and control the live stream behavior through `LiveCoreController`.
 
    ``` java
    import 'package:flutter/material.dart';
@@ -138,7 +138,7 @@ The anchor starts live streaming process is as follows. You just need to perform
      void initState() {
        super.initState();
        // 2. Initialize the controller
-       _controller = LiveCoreController.create();
+       _controller = LiveCoreController.create(CoreViewType.pushView);
        // 3. Set up live streaming ID
        _controller.setLiveID(widget.liveId);
      }
@@ -159,7 +159,7 @@ The anchor starts live streaming process is as follows. You just need to perform
    ```
 2. **Turn on the camera and microphone**
 
-   By calling the **DeviceStore**`openLocalCamera` and `openLocalMicrophone` APIs to turn on the camera and microphone, **no need to do additional configuration as LiveCoreWidget will auto preview the current camera's video stream**. Sample code:
+   Call `DeviceStore.shared.openLocalCamera` and `DeviceStore.shared.openLocalMicrophone` to enable the camera and microphone. LiveCoreWidget will automatically preview the camera video stream:
 
    ``` java
    import 'package:flutter/material.dart';
@@ -181,7 +181,7 @@ The anchor starts live streaming process is as follows. You just need to perform
      @override
      void initState() {
        super.initState();
-       _controller = LiveCoreController.create();
+       _controller = LiveCoreController.create(CoreViewType.pushView);
        _controller.setLiveID(widget.liveId);
        // Turn on the device
        _openDevices();
@@ -208,7 +208,7 @@ The anchor starts live streaming process is as follows. You just need to perform
    ```
 3. **Start live streaming**
 
-   By calling the **LiveListStore**`createLive` API to start video live streaming, sample code:
+   By calling the **LiveListStore**`createLive` API to start video live streaming:
 
    ``` java
    import 'package:flutter/material.dart';
@@ -230,7 +230,7 @@ The anchor starts live streaming process is as follows. You just need to perform
      @override
      void initState() {
        super.initState();
-       _controller = LiveCoreController.create();
+       _controller = LiveCoreController.create(CoreViewType.pushView);
        _controller.setLiveID(widget.liveId);
        _openDevices();
      }
@@ -247,11 +247,9 @@ The anchor starts live streaming process is as follows. You just need to perform
          // Set up live streaming room id
          liveID: widget.liveId,
          // Set up live streaming room name
-         liveName: "test live stream",
-         // Configure the layout template, default: 600 dynamic grid layout
-         seatLayoutTemplateID: 600,
-         // Configure the anchor to always stay on the seat
-         keepOwnerOnSeat: true,
+         liveName: "Atomic Live Demo",
+         // Layout mode: VideoDynamicGrid9Seats represents a dynamic 9-grid layout.
+         seatTemplate: VideoDynamicGrid9Seats(),
        );
 
        // 2. Call LiveListStore.shared.createLive to start live streaming
@@ -289,29 +287,26 @@ The anchor starts live streaming process is as follows. You just need to perform
    }
    ```
 
-   **LiveInfo parameter description:**
+   **LiveInfo parameters:**
 
-| **Parameter Name** | **Type** | **Attribute** | **Description** |
+| <strong>Parameter Name</strong> | <strong>Type</strong> | <strong>Attribute</strong> | <strong>Description</strong> |
 | --- | --- | --- | --- |
-| `liveID` | `String` | Required | Unique identifier for the live streaming room. |
-| `liveName` | `String` | Optional. | Title of the live streaming room. |
-| `notice` | `String` | Optional. | Announcement information of the live streaming room. |
-| `isMessageDisable` | `bool` | Optional. | Whether to mute (`true`: yes, `false`: no). |
-| `isPublicVisible` | `bool` | Optional. | Whether publicly visible (`true`: yes, `false`: no). |
-| `isSeatEnabled` | `bool` | Optional. | Whether to enable the seat feature (`true`: yes, `false`: no). |
-| `keepOwnerOnSeat` | `bool` | Optional. | Whether to keep the room owner on the seat. |
-| `maxSeatCount` | `int` | Optional. | Maximum number of microphones. |
-| `seatMode` | `TakeSeatMode` | Optional. | Microphone mode (`TakeSeatMode.free`: Free to Join the Podium, `TakeSeatMode.apply`: Request to speak). |
-| `seatLayoutTemplateID` | `int` | Required | layout template ID. |
-| `coverURL` | `String` | Optional. | Thumbnail URL of the live streaming room. |
-| `backgroundURL` | `String` | Optional. | Background image URL of the live streaming room. |
-| `categoryList` | `List<int>` | Optional. | Tag list of categories in the live streaming room. |
-| `activityStatus` | `int` | Optional. | Live stream status. |
-| `isGiftEnabled` | `bool` | Optional. | Whether to enable the gift function (`true`: yes, `false`: no). |
+| <code>liveID</code> | <code>String</code> | Required | Unique identifier for the live streaming room. |
+| <code>liveName</code> | <code>String</code> | Optional. | Name of the live streaming room. |
+| <code>notice</code> | <code>String</code> | Optional. | Announcement information of the live streaming room. |
+| <code>isMessageDisable</code> | <code>bool</code> | Optional. | Whether to mute (<code>true</code>: yes, <code>false</code>: no). |
+| <code>isPublicVisible</code> | <code>bool</code> | Optional. | Whether the live room is publicly visible (<code>true</code>: yes, <code>false</code>: no). |
+| <code>seatMode</code> | <code>TakeSeatMode</code> | Optional. | Seat mode:<br>- <code>TakeSeatMode.free</code>: free seat.<br>- <code>TakeSeatMode.apply</code>: apply for seat. |
+| <code>seatTemplate</code> | <code>SeatLayoutTemplate</code> | Required | Seat layout template. |
+| <code>coverURL</code> | <code>String</code> | Optional. | Cover image URL of the live streaming room. |
+| <code>backgroundURL</code> | <code>String</code> | Optional. | Background image URL of the live streaming room. |
+| <code>categoryList</code> | <code>List<int></code> | Optional. | Category tags for the live room. |
+| <code>activityStatus</code> | <code>int</code> | Optional. | Live stream status. |
+| <code>isGiftEnabled</code> | <code>bool</code> | Optional. | Whether to enable the gift function (<code>true</code>: yes, <code>false</code>: no). |
 
 4. **End live streaming**
 
-   After the live streaming ends, the Anchor can call the **LiveListStore**'s `endLive` API to end the live stream. The SDK will handle the logic of stopping streaming and room termination.
+   When the live stream ends, call `LiveListStore.shared.endLive` to stop streaming and close the room. The SDK will handle cleanup automatically.
 
    ``` java
    import 'package:flutter/material.dart';
@@ -345,17 +340,17 @@ The anchor starts live streaming process is as follows. You just need to perform
    }
    ```
 
-### Step 2: Implement Audience Join and Watch
+### Step 2: Audience Room Entry and Viewing
 
-The audience viewing process is as follows. In just a few simple steps, you can achieve audience watching live.
+Enable audience live viewing with these steps:
 
 > **Note:**
 >
 
-> For the business code of audience enter room to pull stream, you can also refer to the [audience_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/audience/audience_widget.dart) file in the TUILiveKit open-source project to understand the complete implementation logic.
+> For a complete audience implementation, see [audience_widget.dart](https://github.com/Tencent-RTC/TUIKit_Flutter/blob/main/live/livekit/lib/live_stream/features/audience/audience_widget.dart) in the TUILiveKit open-source project.
 >
 
-1. **Implement the audience pull stream page**
+1. **Audience Streaming Page**
 
    On your audience page, create a `LiveCoreWidget` instance and control the live stream behavior through `LiveCoreController`.
 
@@ -381,7 +376,7 @@ The audience viewing process is as follows. In just a few simple steps, you can
      void initState() {
        super.initState();
        // 2. Initialize the controller
-       _controller = LiveCoreController.create();
+       _controller = LiveCoreController.create(CoreViewType.playView);
        // 3. Bind live streaming id
        _controller.setLiveID(widget.liveId);
      }
@@ -399,9 +394,9 @@ The audience viewing process is as follows. In just a few simple steps, you can
      }
    }
    ```
-2. **Enter live room to watch**
+2. **Join Live Room**
 
-   By calling the **LiveListStore**`joinLive` API to join the live stream, **no need to do additional configuration, LiveCoreWidget will autoplay the current room video stream**, sample code:
+   Call `LiveListStore.shared.joinLive` to join the live stream. LiveCoreWidget will automatically play the video stream:
 
    ``` java
    import 'package:flutter/material.dart';
@@ -423,7 +418,7 @@ The audience viewing process is as follows. In just a few simple steps, you can
      @override
      void initState() {
        super.initState();
-       _controller = LiveCoreController.create();
+       _controller = LiveCoreController.create(CoreViewType.playView);
        _controller.setLiveID(widget.liveId);
        // Enter live room
        _joinLive();
@@ -455,9 +450,9 @@ The audience viewing process is as follows. In just a few simple steps, you can
      }
    }
    ```
-3. **Log out of live stream**
+3. **Leave Live Room**
 
-   When the audience exits the live streaming room, they need to call the **LiveListStore**'s `leaveLive` API to exit the live stream. The SDK will automatically stop pulling streams and leave the room.
+   When the audience leaves, call `LiveListStore.shared.leaveLive` to exit. The SDK will stop streaming and leave the room automatically.
 
    ``` java
    import 'package:flutter/material.dart';
@@ -493,9 +488,9 @@ The audience viewing process is as follows. In just a few simple steps, you can
 
 ### Step 3: Listen for Live Events
 
-After the audience joins the live room, you also need to process some passive events inside the room. For example, the Anchor proactively ends the live stream, or the audience is kicked out of the room due to rule violation. If these events are not listened to, the client UI may stay on a black screen webpage, affecting user experience.
+After the audience enters the live room, you should handle passive events such as the host ending the stream or the audience being kicked out. Without event handling, the audience UI may remain on a black screen, impacting user experience.
 
-You can achieve event monitoring through `LiveListListener`.
+Use `LiveListListener` to listen for live events:
 ``` java
 import 'package:flutter/material.dart';
 import 'package:atomic_x_core/atomicxcore.dart';
@@ -518,7 +513,7 @@ class _YourAudiencePageState extends State<YourAudiencePage> {
   @override
   void initState() {
     super.initState();
-    _controller = LiveCoreController.create();
+    _controller = LiveCoreController.create(CoreViewType.playView);
     _controller.setLiveID(widget.liveId);
     // 2. Listen to Live Event
     _setupLiveEventListener();
@@ -585,8 +580,8 @@ class _YourAudiencePageState extends State<YourAudiencePage> {
 
 ### Run and Test
 
-After integrating `LiveCoreWidget`, you will obtain a pure video rendering view with complete live streaming business capability but no interactive UI. You can refer to the next chapter Enrich Live-Streaming Scenarios to refine live broadcasting scenarios.
-|  | **Dynamic Grid Layout** | **Floating Window Layout** | **Fixed Grid Layout** |
+After integrating LiveCoreWidget, you’ll have a clean video rendering view with full live streaming capabilities, but no interactive UI. See the next section, Enrich Live-Streaming Scenarios, to add more features to your live stream.
+| Layout | <strong>Dynamic Grid Layout</strong> | <strong>Floating Window Layout</strong> | <strong>Fixed Grid Layout</strong> |
 | --- | --- | --- | --- |
 | Template ID | 600 | 601 | 800 |
 | Description | Default layout; grid size adjusts dynamically based on number of co-hosts. | Co-hosts are displayed as floating windows. | Fixed number of co-hosts; each occupies a fixed grid. |
@@ -595,29 +590,31 @@ After integrating `LiveCoreWidget`, you will obtain a pure video rendering view
 ## Enrich Live Streaming Scenarios
 
 Once the basic live streaming functionality is in place, refer to the following guides to add interactive features to your live stream:
-| **Feature** | **Description** | **Store** | **Implementation Guide** |
-| --- | --- | --- | --- |
-| **Enable Audience Audio/Video Co-hosting** | Audience can apply to join the host and interact via real-time video. | [CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) | Implementation Guide |
-| **Enable Host Cross-room PK** | Hosts from different rooms can connect for interaction or PK. | [CoHostStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_host_store/CoHostStore-class.html) / [BattleStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_battle_store/BattleStore-class.html) | Implementation Guide |
-| **Add Bullet Chat Feature** | Audience can send and receive real-time text messages in the live room. | [BarrageStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html) | Implementation Guide |
-| **Build a Gift Giving System** | Audience can send virtual gifts to the host, increasing engagement and fun. | [GiftStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html) | Implementation Guide |
+
+|**Feature**|**Description**|**Store**|**Implementation Guide**|
+|---------|---------|---------|---------|
+|**Audience Audio/Video Co-hosting**|Audience can apply to join the host and interact via real-time video.|[CoGuestStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html)|Implementation Guide|
+|**Host Cross-room PK**|Hosts from different rooms can connect for interaction or PK.|[CoHostStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_host_store/CoHostStore-class.html) / [BattleStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_battle_store/BattleStore-class.html)|Implementation Guide|
+|**Live Comments Chat**|Audience can send and receive real-time text messages in the live room.|[BarrageStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html)|Implementation Guide|
+|**Gift System**|Audience can send virtual gifts to the host, increasing engagement and fun.|[GiftStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html)|Implementation Guide|
 
 ## API documentation
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| **LiveCoreWidget** | The core view component for live video stream display and interaction: responsible for video stream rendering and view widget processing, supporting scenarios like live streaming, audience co-broadcasting, and anchor connection. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html) |
-| **LiveCoreController** | The controller of LiveCoreWidget: used to set up the live streaming ID, control the preview, and perform other operations. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html) |
-| **LiveListStore** | Full lifecycle management of live streaming room: create/join/leave/terminate room, query room list, modify live information (name, notice), listen to live status (for example, being kicked out, ended). | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) |
-| **DeviceStore** | Audio/Video device control: microphone (on/off, volume), camera (on/off, switchover, video quality), screen sharing, monitor device status in real time. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html) |
-| **CoGuestStore** | Audience co-broadcasting management: join microphone application/invite/grant/deny, attendee permission control (microphone/camera), state synchronization. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html) |
-| **CoHostStore** | Anchor cross-room connection: supports multiple layout templates (dynamic grid, etc.), initiate/accept/reject connection, and manage interactive co-broadcasting with Anchors. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_host_store/CoHostStore-class.html) |
-| **BattleStore** | Anchor PK battle: trigger PK (duration configuration/competitor), manage PK status (start/End), synchronize score, listen to battle results. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_battle_store/BattleStore-class.html) |
-| **GiftStore** | Gift interaction: get gift list, send/receive gifts, listen to gift events (including sender, gift details). | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html) |
-| **BarrageStore** | Danmaku function: send text/custom barrage item, maintain bullet screen list, monitor bullet screen status in real time. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html) |
-| **LikeStore** | Like interaction: send likes, listen to like events, sync total likes. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_like_store/LikeStore-class.html) |
-| **LiveAudienceStore** | Audience management: get real-time audience list (ID/name/avatar), check audience size, listen to Enter/Exit Event. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html) |
-| **AudioEffectStore** | Audio effects: voice-changing (child voice/male voice), reverberation (KTV), ear monitoring adjustment, switch effects in real time. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html) |
-| **BaseBeautyStore** | Basic beauty filter: adjust skin smoothing/whitening/rosy (0-100 levels), reset beauty effect status, synchronize effect parameters. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_base_beauty_store/BaseBeautyStore-class.html) |
+
+|**Store/Component**|Feature Description|API Documentation|
+|---------|---------|---------|
+|**LiveCoreWidget**|Core view for live video display and interaction: handles video rendering and widget management; supports host streaming, audience co-hosting, host cross-room connections, and more.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html)|
+|**LiveCoreController**|Controller for LiveCoreWidget: set live stream ID, control preview, and other operations.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html)|
+|**LiveListStore**|Live room lifecycle management: create, join, leave, destroy room; query room list; update live info (name, announcement, etc.); listen for live status (kicked out, ended).|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html)|
+|**DeviceStore**|Audio/video device control: microphone (toggle/volume), camera (toggle/switch camera/video quality), screen sharing, real-time device status monitoring.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_device_store/DeviceStore-class.html)|
+|**CoGuestStore**|Audience co-host management: co-host application/invitation/accept/reject, member permissions (microphone/camera), status sync.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_guest_store/CoGuestStore-class.html)|
+|**CoHostStore**|Host cross-room connection: supports multiple layouts (dynamic grid, etc.), initiate/accept/reject connection, co-host interaction management.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_co_host_store/CoHostStore-class.html)|
+|**BattleStore**|Host PK battles: initiate PK (set duration/opponent), manage PK status (start/end), sync scores, listen for results.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_battle_store/BattleStore-class.html)|
+|**GiftStore**|Gift interaction: get gift list, send/receive gifts, listen for gift events (including sender and gift details).|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_gift_gift_store/GiftStore-class.html)|
+|**BarrageStore**|Live comments: send text/custom comments, manage comment list, monitor comment status in real time.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_barrage_barrage_store/BarrageStore-class.html)|
+|**LikeStore**|Like interaction: send likes, listen for like events, sync total like count.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_like_store/LikeStore-class.html)|
+|**LiveAudienceStore**|Audience management: get real-time audience list (ID/name/avatar), count audience, listen for audience enter/leave events.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_audience_store/LiveAudienceStore-class.html)|
+|**AudioEffectStore**|Audio effects: voice changer (child/male), reverb (KTV, etc.), ear monitoring, real-time effect switching.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_audio_effect_store/AudioEffectStore-class.html)|
+|**BaseBeautyStore**|Basic beauty filters: adjust smoothing/whitening/rosy (0-100), reset beauty status, sync effect parameters.|[API Documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_device_base_beauty_store/BaseBeautyStore-class.html)|
 
 ## FAQs
 

package/resource/{doc → knowledge}/livekit/core-sdk/live/flutter/live-live-list.md

@@ -1,11 +1,11 @@
-`LiveListStore` is the `AtomicXCore` core module for management of live room list, creation, joining and room status maintenance. With `LiveListStore`, you can build complete lifecycle management for your application.
+`LiveListStore` is the central module in `AtomicXCore` for managing live room lists and handling all aspects of live room lifecycle, including creation, entry, and state maintenance. Use `LiveListStore` to implement robust live streaming lifecycle management in your application.
 
 ## Core Features
 - **Get live room list**: Obtain the current list of all public live rooms, supporting load by page.
 
 - **Live stream lifecycle management**: Provides a complete process API for creation, going live, joining, leaving, and ending live stream.
 
-- **Live stream information update**: Anchors can update publicly available information in the live streaming room at any time, such as cover and notice.
+- **Live stream information update**: Hosts can update publicly available information in the live streaming room at any time, such as cover and notice.
 
 - **Real-time event monitoring**: Listen to key events such as live streaming end and users being kicked out.
 
@@ -14,21 +14,22 @@
 ## Core Concepts
 
 Before starting integration, let's learn about several core concepts related to `LiveListStore` in the following table:
-| **Core Concepts** | **Type** | **Core Responsibilities and Description** |
-| --- | --- | --- |
-| [LiveInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveInfo-class.html) | `class` | Represents the information model of a live room. It contains live ID (`liveID`), name (`liveName`), room owner information (`liveOwner`) and custom metadata (`metaData`). |
-| [LiveListState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListState-class.html) | `class` | Represents the current status of the live list module. Its core attribute `liveList` is a `ValueListenable<List<LiveInfo>>` data type, storing the fetched live stream list. `currentLive` represents the live room information where the user currently resides. |
-| [LiveListListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListListener-class.html) | `class` | Represents the global event listener for a live streaming room. It includes two callbacks, `onLiveEnded` (live streaming end) and `onKickedOutOfLive` (kicked out of live), used to process key room status updates. |
-| [LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) | `class` | This is the core management class for interaction with the live list and room lifecycle. It is a Global Singleton (`shared`), responsible for all live streaming room operations such as create, join, and information update. |
+
+|**Core Concepts**|**Type**|**Core Responsibilities and Description**|
+|---------|---------|---------|
+|[LiveInfo](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveInfo-class.html)|`class`|Represents the information model of a live room. It contains live ID (`liveID`), name (`liveName`), room owner information (`liveOwner`) and custom metadata (`metaData`).|
+|[LiveListState](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListState-class.html)|`class`|Represents the current status of the live list module. Its core attribute `liveList` is a `ValueListenable<List<LiveInfo>>` data type, storing the fetched live stream list. `currentLive` represents the live room information where the user currently resides.|
+|[LiveListListener](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListListener-class.html)|`class`|Represents the global event listener for a live streaming room. It includes two callbacks, `onLiveEnded` (live streaming end) and `onKickedOutOfLive` (kicked out of live), used to process key room status updates.|
+|[LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html)|`class`|This is the core management class for interaction with the live list and room lifecycle. It is a Global Singleton (`shared`), responsible for all live streaming room operations such as create, join, and information update.|
 
 ## Implementation Steps
 
-### Step 1: Integrating the Component
-- **Live streaming**: Refer to quick integration with **AtomicXCore**, and complete the feature implementation for Anchor starts live streaming and audience viewing.
+### Step 1: Integrate the Component
+- **Live streaming**: Refer to Quick Integration with **AtomicXCore**, and complete the feature implementation for Go Live (Host) and audience viewing.
 
-- **Voice chat room**: Refer to quick integration with **AtomicXCore**, and complete the feature implementation for Anchor starts live streaming and audience listening.
+- **Voice chat room**: Refer to Quick Integration with **AtomicXCore**, and complete the feature implementation for Go Live (Host) and audience listening.
 
-### Step 2: Audience Entering the Live Room Implementation
+### Step 2: Implement Audience Entry to Live Room
 
 Create a page to display a live broadcast list. This page uses `GridView` to layout live streaming room cards. When a user clicks a certain card, get the `liveID` of the room and navigate to the audience viewing page.
 ``` java
@@ -285,27 +286,28 @@ class YourAudiencePage extends StatelessWidget {
 }
 ```
 
-**LiveInfo Parameter Description**
-| **Parameter Name** | **Type** | **Description** |
-| --- | --- | --- |
-| `liveID` | `String` | Unique identifier of the live streaming room |
-| `liveName` | `String` | Title of the live streaming room |
-| `coverURL` | `String` | Thumbnail URL of the live streaming room |
-| `liveOwner` | `LiveUserInfo` | Room owner's personal info |
-| `totalViewerCount` | `int` | Total viewers in the live streaming room |
-| `categoryList` | `List<int>` | Category tag list of the live streaming room |
-| `notice` | `String` | Announcement information in the live streaming room |
-| `metaData` | `Map<String, String>` | Custom metadata for complex business scenarios |
+**LiveInfo Parameters**
+
+|**Parameter Name**|**Type**|**Description**|
+|---------|---------|---------|
+|`liveID`|`String`|Unique identifier of the live streaming room.|
+|`liveName`|`String`|Title of the live streaming room.|
+|`coverURL`|`String`|Thumbnail URL of the live streaming room.|
+|`liveOwner`|`LiveUserInfo`|Room owner's personal info.|
+|`totalViewerCount`|`int`|Total viewers in the live streaming room.|
+|`categoryList`|`List<int>`|Category tag list of the live streaming room.|
+|`notice`|`String`|Announcement information in the live streaming room.|
+|`metaData`|`Map<String, String>`|Custom metadata for complex business scenarios.|
 
-## Advanced Features
+## Advanced Usage
 
-### Scenario One: Categorize Live Broadcast List
+### Scenario 1: Categorized Live Room List
 
 On the live square page of the App, the top section features category tags such as "Popular," "Music," and "Gaming." When users click different tags, the live stream list below dynamically filters to show only live streaming rooms of the corresponding category, thereby helping users quickly identify content of interest.
 
-#### Implementation Method
+#### How It Works
 
-The core is to use the `categoryList` property in the `LiveInfo` model. When the anchor starts live streaming and sets the category, the `LiveInfo` object returned by `fetchLiveList` will contain this classification information. After your App obtains the complete live list, just perform a simple filter on the client according to the user's selected category, then refresh the UI.
+The core is to use the `categoryList` property in the `LiveInfo` model. When the host starts live streaming and sets the category, the `LiveInfo` object returned by `fetchLiveList` will contain this classification information. After your App obtains the complete live list, just perform a simple filter on the client according to the user's selected category, then refresh the UI.
 
 #### Sample Code
 
@@ -492,13 +494,13 @@ class _CategoryLiveListPageState extends State<CategoryLiveListPage> {
 }
 ```
 
-### Scenario Two: Show Product Information in Live Shopping
+### Scenario 2: Show Product Information in Live Shopping
 
-In an ecommerce live stream, the Anchor is explaining a product. At this point, a product card pops up at the bottom of the live stream for ALL audience, displaying the product image, name and price in real time. When the Anchor switches to the next product, the card on the client side updates automatically and synchronously.
+During e-commerce live streaming, when the host introduces a product, a product card appears below the live video for all viewers, showing the product image, name, and price in real time. When the host switches products, the product card is instantly synchronized across all audience clients.
 
-#### Implementation Method
+#### How It Works
 
-The Anchor sets the current product's structured information (recommend using **JSON** format) to a custom key (such as "`product_info`") through the `updateLiveMetaData` API setting. **AtomicXCore** will synchronize this update to ALL audience in real time. The client just needs to subscribe to `LiveListState.currentLive`, listen for changes in `metaData`, and once `product_info` is found updated, parse the JSON data and refresh the product card UI.
+On the host side, set the current product's structured information (preferably in JSON format) to a custom key (for example, "product_info") using the `updateLiveMetaData` API. AtomicXCore will instantly sync this data to all viewers. On the audience side, subscribe to `LiveListState.currentLive` and listen for changes in metaData. When product_info updates, parse the JSON and refresh the product card UI.
 
 #### Sample Code
 ``` java
@@ -539,7 +541,7 @@ class Product {
   }
 }
 
-/// Anchor: Push product information
+/// Host: Push product information
 class HostProductController {
   final _liveListStore = LiveListStore.shared;
 
@@ -698,16 +700,17 @@ class _ProductCardWidgetState extends State<ProductCardWidget> {
 
 ## API documentation
 
-For detailed information about ALL public interfaces, properties and methods of [LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) and its related classes, please refer to the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Store used in this document is as follows:
-| **Store/Component** | **Feature Description** | **API Reference** |
-| --- | --- | --- |
-| **LiveCoreWidget** | The core view component for live video stream display and interaction: responsible for video stream rendering and view widget processing, supporting live streaming, audience mic connection, Anchor Connection (TUILiveKit), and other scenarios. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html) |
-| **LiveCoreController** | Controller for LiveCoreWidget: used to set up live streaming ID, control preview, and perform other operations. | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html) |
-| **LiveListStore** | Full lifecycle management of live streaming room: create/join/leave/terminate room, query room list, modify live information (name, notice), listen to live streaming status (for example being kicked out, ended). | [API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) |
+For detailed information about all public interfaces, properties and methods of [LiveListStore](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html) and its related classes, please refer to the official API documentation of the [AtomicXCore](https://tencent-rtc.github.io/TUIKit_Flutter/index.html) framework. The related Store used in this document is as follows:
+
+|**Store/Component**|**Feature Description**|**API Reference**|
+|---------|---------|---------|
+|**LiveCoreWidget**|The core view component for live video stream display and interaction: responsible for video stream rendering and view widget processing, supporting live streaming, audience mic connection, Host Connection (TUILiveKit), and other scenarios.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreWidget-class.html)|
+|**LiveCoreController**|Controller for LiveCoreWidget: used to set up live streaming ID, control preview, and perform other operations.|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_view_live_live_core_widget/LiveCoreController-class.html)|
+|**LiveListStore**|Full lifecycle management of live streaming room: create/join/leave/terminate room, query room list, modify live information (name, notice), listen to live streaming status (for example being kicked out, ended).|[API documentation](https://tencent-rtc.github.io/TUIKit_Flutter/api_live_live_list_store/LiveListStore-class.html)|
 
 ## FAQs
 
-### What Are the Limitations and Rules to Note When Using `UpdateLiveMetaData`?
+### What restrictions and rules apply to updateLiveMetaData?
 
 To ensure system stability and efficiency, the usage of `metaData` follows the following rules:
 - **Permission**: Only the room owner and admin can call the API `updateLiveMetaData`. General audience has no permission.
@@ -720,4 +723,4 @@ To ensure system stability and efficiency, the usage of `metaData` follows the f
 
   - The total size of ALL values in a single room is no more than **16KB**.
 
-- **Conflict resolution**: The update mechanism for `metaData` is "last write wins". If multiple administrators modify the same key in a short time frame, the last modification will take effect. It is advisable to avoid multiple users simultaneously adjusting the same key information in service design.
+- **Conflict Handling**: The update mechanism for metaData is "last write wins." If multiple administrators modify the same key in quick succession, the latest change is applied. To avoid conflicts, design your business logic so that only one person modifies a given key at a time.

package/resource/{doc → knowledge}/livekit/core-sdk/live/ios/live-audience-list.md

@@ -12,12 +12,12 @@
 - **Room Management**: The host or administrator can remove specific viewers from the live room.
 
 ## Core Concepts
-| **Core Concept** | **Type** | **Core Responsibilities & Description** |
+| <strong>Core Concept</strong> | <strong>Type</strong> | <strong>Core Responsibilities & Description</strong> |
 | --- | --- | --- |
-| `LiveUserInfo` | `class` | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
-| `LiveAudienceState` | `struct` | - State container for the audience module.<br>- Exposes `audienceList` (StateFlow) for the real-time user list and `audienceCount` for the total viewer count. |
-| `LiveAudienceEvent` | `enum` | - Event listener for audience changes.<br>- Provides callbacks like `.onAudienceJoined` and` .onAudienceLeft` to handle incremental list updates. |
-| `LiveAudienceStore` | `class` | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
+| <code>LiveUserInfo</code> | <code>class</code> | - Data model representing a viewer.<br>- Contains basic profile information such as userID, userName, and avatarURL. |
+| <code>LiveAudienceState</code> | <code>struct</code> | - State container for the audience module.<br>- Exposes <code>audienceList</code> (StateFlow) for the real-time user list and <code>audienceCount</code> for the total viewer count. |
+| <code>LiveAudienceEvent</code> | <code>enum</code> | - Event listener for audience changes.<br>- Provides callbacks like <code>.onAudienceJoined</code> and<code> .onAudienceLeft</code> to handle incremental list updates. |
+| <code>LiveAudienceStore</code> | <code>class</code> | - Primary interface for audience management.<br>- Used to fetch list snapshots, perform admin operations (e.g., kicking users), and subscribe to real-time events. |
 
 ## Implementation
 
@@ -235,11 +235,12 @@ When a new audience member enters the live room, a welcome message is automatica
 ## API Documentation
 
 For detailed information on all public interfaces, properties, and methods of [LiveAudienceStore](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) and its related classes, refer to the official API documentation included with the [AtomicX Core](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore) framework. The relevant Stores used in this document are as follows:
-| **Store/Component** | **Feature Description** | **API Documentation** |
-| --- | --- | --- |
-| LiveCoreView | Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview) |
-| LiveAudienceStore | Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore) |
-| BarrageStore | Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time. | [API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore) |
+
+|**Store/Component**|**Feature Description**|**API Documentation**|
+|---------|---------|---------|
+|LiveCoreView|Core view component for live video stream display and interaction: responsible for video stream rendering and view widget handling, supporting scenarios such as host streaming, audience co-hosting, and host-to-host connection.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/livecoreview)|
+|LiveAudienceStore|Audience management: obtain real-time audience list (ID / name / avatar), count audience numbers, and listen for audience join/leave events.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/liveaudiencestore)|
+|BarrageStore|Barrage feature: send text/custom barrage, maintain barrage list, and listen to barrage status in real time.|[API Documentation](https://tencent-rtc.github.io/TUIKit_iOS/documentation/atomicxcore/barragestore)|
 
 ## FAQs