In this post, we'll explore how to do two things: 1) create live chat message bubbles in Android that are similar to WhatsApp and iMessage and 2) customize Stream Chat's UI Components.
We'll customize Stream Chat Android's built-in UI components by plugging in a custom message view. This allows us to focus on the text rendering, while Stream does everything else.
The source code is available here. Once we're finished, we'll have a chat experience that looks like this:
This post assumes a working knowledge of Android and Kotlin. If you're unfamiliar with either or both, it may be useful to check out a getting started guide. If you'd like to run the code, you'll also need a Stream account. Please register here. Once you're registered, you'll see a Stream app with an App ID, API Key, and API Secret:
We won't be going through how to create the backend to receive our tokens in this tutorial; please refer to this repo for token generation. You can also use Stream's CLI; if you look in
MainActivity.kt, you'll see placeholders to fill in run the application.
First, we'll create a view which displays a list of channels for a user to select:
This view is mostly taken care of by Stream's UI Components. To list our channels, the
MainActivity.kt will leverage Stream's
ChannelList, and we'll configure it to load all of the channels for our user. Here's the code:
First, we initialize our
StreamChat instance with our API key. We configure it with the user who'll be using our application. To keep things simple, we'll just declare who's logged in and their frontend token. In a real application, you'd want to perform authentication with a backend that generates this token.
We also give the user an
name, and an
image(profile image). Once we've done this, we can declare the layout as "
Now, the view needs a view model; in this case, we'll simply use the default, Stream-provided "
ChannelListViewModel". This is great, as it does all the work to interact with Stream's API. We simply need to configure it to
filter for our user's channels.
The last thing we do is set a "click listener" on each channel. We boot a
ChannelActivity, which is where we'll customize the chat messages. Before we look at the code for
ChannelActivity let's look at the layout:
We use a
ConstraintLayout to hold our
ChannelListView and associated
ProgressBars. Since the view is mostly taken care of by Stream, we just need to configure when it is that our
ProgressBars show and what our
Now, we're ready to view a specific channel!
Once a user clicks a channel, our
ChannelActivity starts. Here is the code:
First, we get our channel information off of the
Intent from our
ChannelActivity.newIntent call, in
MainActivity.kt, and, then, below, we set our content view
You'll notice this was another
ConstraintLayout with some views and progress bars; we use Stream's UI Components to build the majority of the view.
ChannelHeaderView gives us a nice header with a channel image and channel name (from the parent).
MessageListView displays our messages, and
MessageInputView gives us a helpful default message input.
We use the built-in Stream view model and feed that to each view. However, we customize the
MessageListView view by providing a custom message view "factory",
BubbleMessageViewHolderFactory. This "factory" hooks into Stream's code to provide a custom view for each message. This class is straightforward since all we're going to do is instantiate our bubble message class,
Now that we're hooked into the view rendering, we can customize our messages to look like iMessage or WhatsApp!
We're ready to declare our custom bubble view. To hook into Stream's components, we need to be a subclass of
BaseMessageListItemViewHolder. Here is the basic class definition:
We're passed a
viewGroup resource from the factory (we will be using "
bubble_message"). Then, this view is referred to by
itemView. From this, we grab our message header (which will just be spacing, in our case), our text view that will hold the message, and our username view. We also have a
ChannelState, which contain data for our Stream message and channel, respectively. Let's check out our view:
This view is quite simple, as it defines the three pieces we referenced before: the header spacing, the username, and the text. Notice there's no bubble logic here. To get the correct colors and shapes, we'll use drawables and some logic in our class to define how the message will look; this layout is simply the scaffolding for us to fill in.
Implementing this abstract class requires us to implement
bind. We'll ignore
setStyle for this tutorial since we'll be defining all of our styles outright.
You can check out
MessageViewListStyleto see all the ways you can customize the components without building your own class; with that said, in this post, we want to explore how to do it ourselves!
Let's dive in! The
bind method is where we configure how the message looks:
We're given a
MessageListItem, which has everything we need to figure out our display. First, we check the type of message. Stream has a few different message types, which represent different things. For example, you may get a message type that indicates a user is typing or a date separator. In our case, we'll focus on two, the actual messages and date separators; we'll ignore any other message type and remove them from rendering, entirely.
Let's focus on the actual messages to start; we'll look at how to render the date separators after. Here is our
We do three things: 1) configure the actual text display, 2) decide if we need to show a username 3) determine how much spacing we have between messages.
First, let's see how we configure the actual text and render our bubble message:
We set the
TextView's text, then decide if it's "our" message or "theirs". If it's "ours", we display the message on the right, in blue. If it's "theirs", it goes on the left, in grey. To set the justification of the message, we use
horizontalBias; setting it to
1 sets the message to the right, and
0 sets the message to the left. We'll also set the text color based on the background since blue needs white text and grey needs black. Padding is also set differently for the two cases, since the message will have the "tail" on the right or left, depending on who's message it is.
Since we're replicating iMessage's style, they don't render the tail unless it's the bottom message. Conveniently, Stream gives us position information and makes it easy to check message placement within a group of messages:
If the message is the bottom message, it means it's the only message or the last in a group of messages by the same user. If it's either of those, we add a tail; if it's not, we just do a simple bubble. We'll also set the background of the text view to a "drawable". Let's look at "our" message drawables; here's the drawable with a tail:
We're doing a bit of a smart trick by defining
layer-list with two items. One is a regular rectangle with rounding, the other is a rotated rectangle that is covered by the standard rectangle. We pad the regular rectangle out to give a small gutter, so the edge of the rotated rectangle sticks out. This gives us a beautiful "tail" for the message bubble.
While we chose to keep it simple here with just rectangles, if you'd like a more stylized tail, such as the one you see in iMessage, you can use vector drawables to convert an SVG to a drawable.
For messages that don't need a tail, we define a simple shape with some spacing for the tail gutter:
Messages for "theirs" is the same pattern but mirrored and grey:
Nice! Now we have some good looking bubbles:
Now we can add the username, if necessary, and space the messages correctly. First, we'll look at
First, we decide if we show the username at all. There are three cases where we want it gone. If it's a 1-on-1 chat, if the message is "ours", or if it's not the top of a group of messages (otherwise, we'd have usernames on every message within a grouping). This logic means we only label groups of messages from other people in group chats.
If we have that case, we set the text of the username
TextView to the user's name. We set the bias and margin depending on if it's on the right or the left.
Now we can space our messages depending on their placement in a group of messages:
This is simple since our default spacing is in our layout resource. We simply shrink the height if we're not the top message. Now you'll see the nice spacing and appropriate tails with usernames in our group chats:
All that's left is to deal with our date separator messages, and we're done! These
MessageListItems come with no user and just a date. These are used to provide a horizontal separator between messages that are spaced out in time. These messages are automatically created by Stream when it decides the time between messages has been too long, and it'd be nice to group them. For example, if you message back a day later, you can break up the view with a date marker to inform the user of roughly when messages have come in. Here's
This is straightforward since our default text view has no styling and the correct spacing. We just need to turn off the username view and add the date. Now we have a convenient date separator:
And we're done! We now have custom bubble messages hooked into Stream.
Replicating iOS style messages on Android is relatively simple with drawables. Stream makes it even simpler with it's out of the box UI Components. You can start with Stream default views and customize them or build your own. If you want full control, you can ignore the UI Components and use the lower level Stream libraries directly. It's easy to peel back the layers when you need it!
For in-depth details on how to use the Stream Chat SDK for Android, check out the interactive tutorial here. You'll learn how to build everything that is required for real-time chat – typing indicators, reactions, threads, etc.
Happy coding! 💬