Goal

Resolves AND-762.

Introduce VideoComponentFactory as the single component override mechanism for the Compose Video SDK, mirroring ChatComponentFactory from the Chat SDK so the customization model is the same across both products. Today customization is spread across per-composable lambda slots, the style layer and the activity delegate; the factory gives one place to override components globally.

Stacked on #1776 (AND-1417). The base will be retargeted to develop after that PR merges, so only the last commit is relevant for review.

Implementation

• VideoComponentFactory: a public interface with 29 @Composable methods, each with a default implementation that renders the built-in component. It covers the components behind the existing lambda slots on CallContent, ParticipantVideo, ControlActions, CallLobby, CallAppBar and the ringing screens.
• VideoComponentFactoryParams.kt: one params holder class per method (29), so methods can grow without breaking overrides. This follows the chat convention, including the params classes from day one (chat had to retrofit them in AND-1119).
• CompoundComponentFactory: layers overrides on top of the current factory for a subtree. Note: chat's version uses remember(keys), which treats the vararg array as a single identity-compared key. This PR uses remember(currentComponentFactory, *keys) instead; the same fix probably applies to the chat SDK.
• Wiring: componentFactory parameter on VideoTheme, a public LocalComponentFactory, and a VideoTheme.componentFactory accessor.
• StreamCallActivityComposeDelegate exposes an overridable componentFactory used by the screens it renders. Screen-level overrides stay on the delegate, component-level overrides live in the factory.
• Demo app sample: DemoComponentFactory replaces the inline reaction and participant-action lambdas that CallScreen passed in two places, and is installed on the demo activity delegate.

Compatibility:

• All existing lambda slots keep their signatures and now delegate to the factory by default, so the change is additive at the source level and the PR can land on develop.
• The new VideoTheme parameter changes its JVM signature, so consumers need a recompile against this version. The rest of the api dump diff is additions only.

Decisions that deviate from a literal 1:1 slot mapping:

• The CallAppBar leading/center/trailing slots are separate factory methods instead of nullable fields on CallAppBarParams, because a null field could not distinguish "hide" from "use the default".
• ParticipantLabel's soundIndicatorContent slot is not covered, because its two overloads have different default paddings, so one factory method could not serve both without a visual change.
• The lobby controls method does not delegate to the overridable ControlActions method on purpose, so overriding the in-call bar does not change the pre-join lobby bar.

Out of scope, per the ticket ("Initial method coverage: the slots that already exist as lambdas"): internal render paths that never had lambda slots still call components directly, so a factory override of ParticipantVideo applies to the main grid but not inside the default floating self tile, the default picture-in-picture content or the screen share renderer, and AudioCallContent has no factory methods yet. Tracked in the follow-up ticket AND-1441.

🎨 UI Changes

No visual changes. This is a refactor of how the default slot content is resolved; the snapshot suite must stay identical and it does (no golden regenerated).

Testing

• :stream-video-android-ui-compose:verifyPaparazziDebug passes with no golden regenerated, which is the acceptance criterion for identical rendering of all default paths.
• apiDump updated and apiCheck passes.
• Debug and release compilation of the SDK module, plus the demo app.
• Manual check in the demo app: DemoComponentFactory drives the custom reaction and the Kick participant action through the factory instead of inline lambdas, on the grid tiles and now also on the floating self tile (Kick excludes the local participant).

To test an override without the demo app, pass a factory to the theme:

VideoTheme(
    componentFactory = object : VideoComponentFactory {
        @Composable
        override fun RowScope.CallAppBarTrailingContent(params: CallAppBarTrailingContentParams) {
            // Custom trailing content
        }
    },
) {
    CallContent(call = call)
}

Summary by CodeRabbit

• New Features
  • Added customizable call UI components across app bars, active calls, lobbies, participant video, and incoming/outgoing call screens.
  • Added theme-level controls for replacing or extending default video-call interface elements.
  • Added participant reaction customization, including placement and display duration.
  • Added a capability-gated “Kick” participant action in the demo app.
  • Added customizable participant labels, connection indicators, overlays, captions, moderation UI, and call controls.
• Improvements
  • Updated the demo call screen to use the new customizable components.