Overview

The Compose UI Components library includes pre-built Jetpack Compose components that let you easily load and display data from the Stream Chat API, without much code.

Not using Compose yet? Check out our XML-based UI Components.

Channels Screen (Light Theme)	Messages Screen (Light Theme)

Channels Screen (Dark Theme)	Messages Screen (Dark Theme)

This library builds on top of the offline library and provides three types of components:

• Screen components: Fully built screens that work out-of-the-box, but offer much more limited customization.
• Bound components: Fully built components that represent a part of the screen and are bound to ViewModels we provide, for business logic, events, and state handling. These provide extensive behavior and UI customization.
• Stateless components: Simple components that rely on pure state and know nothing about our ViewModels. Fully customizable.

The sample app showcases the Compose UI Components in action.

See the individual pages for these components to learn more about them.

Channel components:

• Channels Screen
• Channel List Header
• Channel List
• Channel Item
• Selected Channel Menu

Message components:

• Messages Screen
• Message List Header
• Message List
• Message Composer
• Attachments Picker
• Selected Message Menu
• Selected Reactions Menu

Utility components

• User Avatar
• Channel Avatar
• Search Input

Requirements

To use the Compose UI Components, you have to set up your project to work with Jetpack Compose, as per the official documentation.

Once you’re done, add the necessary dependencies, as described on the Dependencies page.

And that’s it!. You should be able to use our Compose UI Components in your app to start building a rich chat experience.

ViewModels

Our bound components require a ViewModel to connect to for state and event handling. Some of our components build the ViewModel by default, but you’ll likely want to build your own instances to gain more control over their lifecycle.

These are Jetpack ViewModels, so they allow the components to retain data across configuration changes. It’s your responsibility to create these in the correct scope, usually in a Fragment or Activity.

For example, if you want to add the MessageList component to your UI, you can do it like so:

// 1
val factory by lazy {
    MessagesViewModelFactory(
        context = this,
        chatClient = ChatClient.instance(),
        channelId = "messaging:123",
        enforceUniqueReactions = true,
        messageLimit = 30
    )
}

// 2
val listViewModel: MessageListViewModel by viewModels { factory }

override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    // 3
    setContent {
        ChatTheme {
            MessageList(
                modifier = Modifier
                    .padding(8.dp)
                    .fillMaxSize(),
                viewModel = listViewModel // 4
            )
        }
    }
}

1. Create the ViewModel factory, providing any necessary parameters.
2. Build the ViewModel, using the Android ViewModel APIs and the factory you created.
3. Set the content of your Activity or Fragment and call the MessageList component.
4. Pass in the ViewModel to the component.

By passing in the ViewModel, the component knows where to fetch the data from and where to delegate various events, like selecting a message or tapping on a thread reply.

You can learn more about each component’s setup and usages on their individual pages.

Sample App

The Compose UI Components sample app is an open-source and fully functional messaging application that lets you explore and test our API. It features channels, threads, reactions, various attachments, UI updates and offline storage.

All built using our Compose UI Components and the offline library.

Customization

Our Compose UI Components offer different ways of customization:

• Behavior: Through event handlers for clicks, taps, dismiss requests and more.
• Appearance: Through different parameters for shapes, colors or a Compose Modifier, you can customize the component appearance.
• Content: Some components provide slot APIs, composable function parameters that let you define (or override) their internal content.
• Design style: By using our ChatTheme component as the root of all of your UI, you can define the colors, typography, shapes, attachment factories, reaction types and various other things our components use. Through this, you can apply your own design style to all Compose UI Components.

To learn what level of customization each component exposes, check out their respective documentation pages. If you want to learn about general customization, read our ChatTheme page.