Introduction

Our Chat UIKit and Social UIKit for Amity Social Cloud is a development kit with a user interface to enable fast integration of standard Amity Chat and Amity Social features into new or existing applications. Themes allow you to apply your style through colors and fonts.

We have now open sourced Amity UIKit so you will have complete control of the visual style of your Chat and Social application with endless customizations. Amity UIKit open source is now available in our Github repository.

To customize Amity UIKit open source, download the source code and apply the customizations in the forked source code. Once you fork our UIKit source code separately, you basically own the product so you are free to customize and build it for your specific use cases.

We recommend that you use Amity UIKit open source when:

1. The standard UIKit is not applicable to your use case.

2. You want to use an Amity Chat or Social SDK feature which is not yet supported in our standard UIKit.

Please note that we will extend only a limited support once you customize our UIKit open source since we won’t be able to fully know your code once you fork it.

Documentation

We are using the Amity UIKit open source wiki for any documentation related to Amity UIKit open source.

For our standard UIKit, you can refer to the documentation here.

Community guidelines

If you would like to suggest improvements on the source code, you can submit a pull request. If you find bugs or would like to request features, you can create an issue. Please note that not all changes and requests will be approved but they will be assessed in due course.

For more information on these guidelines, you may refer to the Amity UIKit open source wiki or you may go directly to these related pages:

• Customizing Amity UIKit Open Source

• Contributing to Amity UIKit Open Source

• Submitting fixes and feature requests

Benefits

• Easy Installation

• Fully featured chat experience with minimal coding

• Customize targeted UX flows, specific views and respond to user interactions to tailor a user experience for just your application

Requirement

• iOS 11.0 or higher

• Swift 5

• Xcode 11.7

Implementation Strategies

The UIKit API provides several strategies to integrate with your application.

Page Presentation

• Use the UIKit as is.

• Integrate the Chat experience in the least amount of effort.

Page Presentation customized

• Add a custom theme to the default implementation of the UIKit.

• Complete control of the visual style of Chat UI by implementing declarative styles (fonts and colors) for your user interface.

Page Integration

• Use key components from the UIKit SDK and integrate them directly into your application.

• Add the Chat UI to your existing design.

Key Concepts

Architecture

The UIKit is built on the foundation of the Amity API while adding a UI layer to speed product development efforts. At the core it is leveraging the same Channel, Messaging concepts, subscribing to live objects whilst adding a UIKit to accelerate product delivery and UI that delivers great user experience for companies wanting to deploy messaging.

In the current state, there are two modules that can be used. You can follow the steps below. These two modules can be integrated into your application easily in no time.

iOS UI Kit Migration Instructions

To allow for more customization, we have now open sourced our UI Kits and deprecated the packaged UI Kit version that was previously available.

With open-source, developers have more flexibility and greater customization options, allowing you to have complete control over the visual style. Open sourcing allows for more transparency and visibility and enables contributions from a greater developer community in terms of good design, implementation, code improvement, and fixes, translating into a better product and typical development.

To ensure that you continue to receive the latest features and updates, we encourage you to move off the managed UI Kit to the Open Source UI Kit. This guide will show you how to:

• Migrate Open Source UI Kit with an existing project

• Modify Open Source UI Kit to customize the visual style

• Get latest Open Source UI Kit updates

Migrate iOS Open Source UI Kit with Existing Project

Remove existing dependencies

If you've never used UI Kit, you may skip this step and proceed to the next step.

If you're integrating the UI Kit with an existing project, you'll need to remove and unlink the managed UIKit from your project before proceeding with the integration.

Migrate to iOS UIKit Open Source

There are several ways for you to migrate the open source iOS UI Kit into your projects, depending on your workflow. One way that we recommend is via Git Submodule. This instruction assumes that the app project is already set up with a Git repository.

1. Add git submodule of Amity UIKit open source into your git repository.

git submodule add https://github.com/AmityCo/ASC-UIKit-iOS-OpenSource

For new users:

If you are just starting to use Open Source UIKit or already using latest version of Open Source UIKit (i.e v3.12.0) from old Repository, We suggest you to start pulling changes from new repository instead.

In this case,

• If you have forked old open source UIKit repository, we suggest you to fork new repository and use that instead.

For Old Users:

If you are using older version (< 3.12.0) of open source UIKit, we suggest you to upgrade to latest version of UIKit as soon as possible. Once you are caught up to version 3.12.0, please migrate to use new repository instead.

1. Create an Xcode Workspace, and then add both MyApp.xcodeproj and AmityUIKit.xcodeproj together under the same workspace.

3.AmityUIKit links with other dependencies such as AmitySDK, Realm etc through SharedFrameworks which is a Swift Package.

Step 1: Reset Package Cache of your Application Target i.e YourApp.xcodeproj. [If you are installing AmityUIKit for the first time, you can skip this step]

Select App Target In Xcode Project -> Select File Menu for Xcode-> Packages -> Reset Package Cache

Step 2: Link SharedFrameworks & AmityUIKit.framework to YourApp.xcodeproj target as shown below.

4. On MyApp.xcodeproj, let’s try importing AmityUIKit / AmitySDK and call some APIs. You should be able to compile and run the app.

Modify iOS Open Source UI Kit

You can modify the iOS open source UI Kit to customize behaviors to fit your needs. To modify the code, simply copy and paste it into your local machine.

We recommend that you first fork the repository before starting any customization work, so that it will be easier to merge the code with the next version update that we provide from the main repository.

References on forking: https://docs.github.com/en/get-started/quickstart/fork-a-repo

Get Latest iOS Open Source UI Kit Updates

To update to the latest version of the UI Kit, you can pull the latest commit of the git submodule.

cd https://github.com/AmityCo/ASC-UIKit-iOS-OpenSource
git pull origin master
cd ..
git add .
git commit -m “Update ios uikit opensource submodule”
git push origin master

Usage

Create a view controller

This section is about installing managed uikit through dependency manager. If you have already installed our Open Source UIKit, you can skip this section.

Create a project

Go to Xcode and create a project for iOS.

1. Enter a project name

2. Select Swift as your language option

Using Dependency Manager

AmityUIKit supports installation via dependency managers, we highly recommend SwiftPM installation as best practice.

• SwiftPM

• Cocoapods

• Carthage

SwiftPM Installation

To integrate AmityUIKit into your project via SwiftPM, please follow the instruction below.

Enter the repository URL to search the package, and choose to install AmityUIKit.

Carthage Installation

Now you can install Amity Social UIKit into your project by running the following command.

Cocoapods Installation

Then, add the following lines to the Podfile

Now you can install Amity Social UIKit into your project.

If problems happen during pod install step. Please try clean Cocoapods cache before running pod install again.

To clear cache please go to ~/Library/Caches/Cocoapods and remove all folders.

Usage

After finished installing SDK. You will be able to import AmityUIKit.

Adding required permissions

Your app may require the following permissions to work properly;

1. Camera access

2. Microphone access

3. Photo library usage access

Before submitting your application to the store, please make sure the following permissions are already granted. Here are the steps to ask for permission.

Locate the info.plist file and add:

1. NSCameraUsageDescription

2. NSMicrophoneUsageDescription

3. NSPhotoLibraryUsageDescription

Setup API key

AmityUIKit requires an API key. You need a valid API key to begin using the UIKit. Please find your account API key in

After logging in Console:

1. Click Settings to expand the menu.

2. Select Security.

3. In the Security page, you can find the API key in the Keys section.

Specify Endpoints Manually (Optional)

By default, AmityClient will connect to AmityRegion.SG. You can specify endpoints manually via AmityEndpoint struct. API endpoints for each data center are different so you need to adjust the endpoint accordingly.

We currently support multi-data center capabilities for the following regions:

Authentication

Register device

To use any SDK feature, you must first register the current device with a userId. A device registered with an userId will be permanently tied to that userId until you explicitly unregister the device, or until the device has been inactive for more than 90 days. A device registered with a specific userId will receive all messages belonging to that user.

Additionally, an optional displayName can be provided if you wish to have this user identified in push notifications.

Register device for push notifications

Registering your app for push notifications will require a device token as a parameter.

Amity's UIKit does not manage:

• User-facing requests for push notifications and authorizations

• The creation and refreshing of push notification tokens

It's up to your app to take those steps and pass the device token.

Unregister

In the event that your user logs out, you should explicitly unregister the user from the SDK as well, to prevent the current device from receiving any unnecessary or restricted data.

Component Customization Limitation

Amity UIKit provides already built UI elements on single page. You can change the appearance such as color and typography, in the global settings. However, the UIKit does not allow you to replace these small components with other views. In addition, you cannot modify the view hierarchy inside the page.

Features

Usage

Create a view controller

let viewController = AmityMyCommunityPreviewViewController.make()

Components

• Explore

• New feed

Usage:

Create a view controller

let viewController = AmityCommunityHomePageViewController.make()

Components

• My Community

• Global feed

Usage

Create a view controller

let viewController = AmityNewsfeedViewController.make()

Features

Usage

You can use either of these two methods:

1. make - the posts will be ranked in chronological order. Below is the sample code.

   Copy

   let viewController = AmityGlobalFeedViewController.make()

2. makeCustomPostRanking - the posts will be ranked according to a score-sorting mechanism. Refer to Custom Post Ranking for more information about this feature. You can retrieve your global feed sorted by ranking score with this code.

   Copy

   let viewController = AmityGlobalFeedViewController.makeCustomPostRanking()

Using the default theme

AmityUIKit uses the default theme as part of the design language.

Theme customization

With no customization, UIKit already looks good. However, if you wish to customize the theme, you can declare changes to both colors and typography.

Colors

UIKit uses a small set of declared colors to simplify the design task for developers. These colors are automatically rendered at appropriate shades to communicate states and interactions to the users.

Usage

To declare your own colors on iOS:

1. Create an instance from the provided class AmityTheme

2. Set the theme instance through AmityUIKitManager

// default colors
let myTheme = AmityTheme()
    
// partially overriding colors
let myTheme = AmityTheme(
    primary: UIColor.systemBlue,
    secondary: UIColor.systemOrange)

// fully overriding colors
let myTheme = AmityTheme(
    primary: UIColor.systemBlue,
    secondary: UIColor.systemOrange,
    alert: UIColor.systemRed,
    highlight: UIColor.systemBlue,
    base: UIColor.white,
    baseInverse: UIColor.black,
    messageBubble: UIColor.systemTeal,
    messageBubbleInverse: UIColor.systemRed)

AmityUIKitManager.set(theme: myTheme)

Typography

The AmityTypography is a class that manages a set of UIFont properties used in Amity UIKit. All fonts used in our UIKit are configured under this class.

Usage

To declare your own typography on iOS:

1. Create an instance from the provided class AmityTypography.

2. Set the typography instance through AmityUIKitManager.

// default typography
let myTypography = AmityTypography()
    
// partially overriding typography
let myTypography = AmityTypography(
    headerLine: UIFont(name: "Georgia-Bold", size: 20)!,
    title: UIFont(name: "Georgia", size: 20)!)

// fully overriding typography
let myTypography = AmityTypography(
    headerLine: UIFont(name: "Georgia-Bold", size: 20)!,
    title: UIFont(name: "Georgia", size: 20)!,
    bodyBold: UIFont.systemFont(ofSize: 16, weight: .regular),
    body: UIFont.systemFont(ofSize: 16, weight: .regular),
    captionBold: UIFont.systemFont(ofSize: 13, weight: .regular),
    caption: UIFont.systemFont(ofSize: 13, weight: .light))

AmityUIKitManager.set(typography: myTypography)

Features

Usage

let viewController = AmityMyCommunityViewController.make()

Features

Usage

Create a view controller

Features

Usage

Create a view controller

Components

Usage

Create a view controller

Features

Usage

Create a view controller

Features

Usage

Create a view controller

let viewController = EkoCategoryCommunityListViewController.make(categoryId: "CATEGORY_ID")

Features

Features

Usage

Create a view controller

Features

Usage

Create a view controller

Feature and Component

Usage

Create a view controller

Features

Features

Features

Text only

Text and Images

Device Camera

Device Image Gallery

Text and Files

Text and Videos

Polls

You can create a poll post and other users can interact with that poll post by selecting from the poll options.

Live Stream

To create a live stream post and for a detailed discussion on the live stream features, refer to Livestream Post documentation.

Features

Supported types

• File: All file types are supported

• Image: JPG, JPEG, and PNG

• Video: 3GP, AVI, FLV, MP4 and MPEG-2

Usage

Create a view controller

// Post to user feed
let viewController = AmityPostCreatorViewController.make(postTarget: .myFeed)

// Post to community feed
let viewController = AmityPostCreatorViewController.make(postTarget: .community(object: postModel))

// Poll post
let viewController = AmityPollCreatorViewController.make(postTarget: <your post target>)
self.present(viewController, animated: true, completion: nil)

Parameter

Attachment options

By default AmityPostCreatorViewController allows all attachments when creating a post. You can optionally choose attachment options when creating the post.

All available attachment options are image, video, and file. These can be found in AmityPostAttachmentType.

// Only allow file attachment in post creator page.
let settings = AmityPostEditorSettings()
settings.allowPostAttachments = [.file]
let postCreator = AmityPostCreatorViewController.make(postTarget: postTarget, settings: settings)

Features

How to use

Create a view controller

let viewController = AmityPostDetailViewController.make(withPostId: "POST_ID")

Link Preview in Post

The Link Preview feature in posts is designed to enrich user experience by providing a visual and informative preview of external links. This feature enhances content sharing, making it more interactive and engaging. This feature significantly improves the user's posting experience. It allows for a preliminary check of the link's accuracy and relevance, adding visual appeal to the post with an informative preview.

When a user includes a link in a post, the feature automatically extracts and displays key information: the title, main image, and a short description, creating an informative preview of the linked content. If the link is unavailable, it will show a empty placeholder or error view instead.

Editing Capability

Users can edit the link preview even after the post is created. This flexibility ensures that the information remains up-to-date and accurate, enhancing the overall quality of the post.

Limitations and Use Cases:

The preview feature is designed to only display images, titles, and descriptions after a post is created. This ensures clarity and relevance in the shared content.

AmityUIKit provides the livestream recording feature that allows you to record livestreams and broadcast simultaneously in real-time. You can also play historical streams when the livestream ends.

This section describes the livestream feature in detail. Refer to our Livestream documentation to enable livestream functionalities.

A livestream post can be viewed in the following feeds:

• Community feed

• User feed

• Global feed

• Content feed

You will be able to see the livestream post and interact with it as soon as the livestreamer starts streaming.

Creating a livestream post

To create a livestream post, follow these steps:

1. Create a livestream post by selecting Livestream from the pop-up and selecting a location where you want to post the stream.

2. Provide a title and description for your livestream. The Go live button will not enable if you don't provide a title and description.
3. Add a cover thumbnail from your media gallery for the livestream post and preview the cover image. This step however is optional. You may also update and delete the cover thumbnail.

   Note: A default cover will be used if no cover thumbnail is selected.

4. Tap Go live to start streaming.
5. There will be a time indicator on the upper left. It will indicate how long it has been since the livestream started.

6. The livestream post will then show in the feed.

7. Tap Finish to end livestreaming. It will then show Ending livestream once the livestream has ended.

   Note: You have the option to edit or delete the livestream post from the feed.

Viewing a livestream post

Live

Other viewers can watch your livestreaming while you are simultaneously recording it. They will see a LIVE indicator on the video.

Tapping the play button in the livestream post will play the video in a full screen mode.

Livestream ended

After ending your livestreaming, the playback video may not be available instantly for viewers to see while it is still in the process of producing the playback video. The viewers will see a message that the playback will be available for watching shortly.

Playback

When the playback video is already available for viewing, a RECORDED indicator is shown on the video post.

Idle state

The livestream may be in idle state. This happens when you delete the livestream in console or or other issues that will not enable the livestreaming to start. The viewer will see a message that the stream is currently unavailable.

Read-only mode

A livestream post will have the same privacy and access controls as with the other posts. This means that users without the permission, such as those who are not members of the community, won’t be able to view the livestreaming/playback video in a private community. If the community is public, non-members can view the post as read only so they won't be able to interact with it.

Permissions

If it's your first time creating a livestream, your device will prompt to allow access to your device's camera and microphone.

You need to allow access to be able to start a livestream. The pop-up below will not show once you allow access to your camera and microphone.

Features

Usage

Create a view controller

The function will create a new instance of AmityCommentEditorViewController.

Parameters

Features

Usage

Create a view controller

Parameter

Features

Usage

Create a view controller

The function will create a new instance of AmityCommentCreatorViewController.

Parameters

Features

Usage

Features

Non-member View

Community Member View

Community Creator View

Components

• Community feed

• Media Gallery

Features

Usage

Create a view controller

let viewController = AmityCommunityProfilePageViewController
.make(withCommunityId: "COMMUNITY_ID")

There are 2 states of User profile page:

1. User's own profile

2. Other User's Profile

Components

• User feed

Features

Usage

let viewController = AmityUserProfilePageViewController.make(withUserId: "USER_ID")

Features

Usage

// Current user feed
let viewController = AmityMyFeedViewController.make()

// Some user feed
let viewController = AmityUserFeedViewController.makeUserFeed(withUserId: "USER_ID")

Features

Usage

let viewController = AmityCommunityMemberSettingsViewController.make(community: community)
navigationController?.pushViewController(viewController, animated: true)

Default User Feed

This view allows user to view and interact with the feed content normally. This also applies when the Privacy setting is Public.

Private User Feed

This view blocks any user to see the target user's feed content. This view only exist if the Private setting is Private.

Features

Usage

User's Own Profile Setting Page

Other User's profile setting page

There are two main state based on the user connection.

If user is already connected with the target user

If user is not connected with the target user

You can try this code:

`

Features

Usage

let viewController = AmityUserProfileEditorViewController.make()

In this page , user will see the list of the following user (users who the target userId has been following) and the follower user(users who follow the target userId).

Features

You can try it with this code:

let vc = AmityUserFollowersViewController.make(withUserId: "userId")
navigationController?.pushViewController(vc, animated: true)

In this page, user can see all the follow request he has received. He can either accept or decline the request as well.

You can use the component with this code:

let requestsViewController = AmityFollowRequestsViewController.make(withUserId: "userId")
navigationController?.pushViewController(requestsViewController, animated: true)

There are two views for the user profile page.

1. User's own profile

This view allows the user to see his own user profile detail and his own user feed, there are two state user can see.

Default state : Allows user to see his own following user counter and Follower user counter.

Request pending state : Allows user to see his own following user counter, Follower user counter, and also the follow request he received.

Components

You can get this view by using this code:

2. Other user's profile

This view allows the user to see other user's profile detail and their user feed. There are two states user can see

In the other user view , UIKIT has two main views that support the Follow user connection and the User privacy view.

Default state : Allows user to see the connection between the current user and the target user profile.

If the current user is NOT connected to the viewing user and Private setting is Public

If the current user is connected to the viewing user and Private setting is Public

If the current user is NOT connected to the viewing user and Private setting is Private

If the current user has send request to the viewing user and Private setting is Private

Components

You can get this view by using this code:

Features

Usage

let vwiewController = AmityMemberPickerViewController.make()
navigationController?.pushViewController(viewController, animated: true)

Features

Usage

UIKIT allows the default behaviour to be overridden by custom logic.

AmityUIKit allows some parts of the component to be customized:

• Post Sharing

• Post Rendering

Post Sharing Settings

This setting allows you to control where a post can be shared to based on the post origin.

There are five possible targets that a post can be shared to

My feed - The post can be shared to my feed. This option will enable "Share to my timeline" menu when user clicks share button.

Public community - The post can be shared to any public community. This option will enable "Share to group" menu when user clicks share button.

Private community - The post can be shared to any private community. This option will enable "Share to group" menu when user clicks share button.

External - The post can be shared externally. This option will enable "More options" menu when user clicks share button.

Origin - The post can be shared within the community feed that it was created. If the post was created in either public or private community, this option will enable "Share to group" menu when user clicks share button.

There are four possible origins

My feed post - Posts that were created on my feed. By default, possible sharing targets are My feed, Public community, and Private community.

User feed post - Posts that were created on any other users' feed. By default, possible sharing targets are My feed, Public community, and Private community.

Public community feed post - Posts that were created on any public community. By default, possible sharing targets are My feed, Public community, and Private community.

Private community feed post - Posts that were created on any private community. By default, possible sharing target is Origin.

Usage

You can select a set of targets for each post origin.

Post Sharing Events

Based on Post sharing settings, there are up to three post sharing events that can be emitted by UIKit.

Share to my timeline - an event emitted when a user clicks on "Share to my timeline" button.

Share to group - an event emitted when a user clicks on "Share to group" button.

Share externally - an event emitted when a user clicks "More options" button.

Usage

You can choose to intercept one or all of the events and apply your custom behavior.

Usage

let communityHomePage = AmityCommunityHomePageViewController.make()
communityHomePage.navigationBarType = .custom

// create custom view
let label = UILabel()
label.text = "This is a navigation custom view"
label.backgroundColor = .orange

// assign custom view to title view
homepage.navigationItem.titleView = label

With our chat functionality in AmityUIKit, you can explore how best to integrate and design messaging features and how they will look in your app.

Custom Post Rendering

UIKit provides default renderers for the core data types: text, image, and file. It also provides a way to render your own UI for your custom post.

Post Structure:

A single post UI is composed of 1 or more UITableViewCell. This allows reusability of cell components such as header or footer which can be shared by different kinds of posts.

This is an example of simple text post which contains 3 tableview cell. Top cell represents the header, middle cell contains text content and bottom cell is footer cell.

Creating UI for custom posts :

There are 3 steps involved in creating custom post renderer.

Step 1: Create your UI using UITableView cells.

class MyPostHeaderCell: UITableViewCell { 
    // ...
}

class MyPostContentCell: UITableViewCell {
    // ...
}

Step 2: Compose a post UI component. For this create a component which conforms to AmityPostComposable protocol.

struct MyCustomPostComponent: AmityPostComposable {
    
    var post: AmityPostModel
    
    // Post data model which you can use to render ui.
    init(post: AmityPostModel) {
        self.post = post
    }
    
    func getComponentCount(for index: Int) -> Int {
        return 2
    }
    
    func getComponentCell(_ tableView: UITableView, at indexPath: IndexPath) -> UITableViewCell {
        switch indexPath.row {
        case 0:
            let cell = tableView.dequeueReusableCell(withIdentifier: "my-cell-identifier", for: indexPath) as! MyPostHeaderCell
            // ... populate cell data here
            return cell
        case 1:
            let cell = tableView.dequeueReusableCell(withIdentifier: "my-cell-identifier", for: indexPath) as! MyPostContentCell
            // ... populate cell data here
            return cell
        default:
						fatalError("indexPath is out of bound")
        }
    }
    
    // Height for each cell component
    func getComponentHeight(indexPath: IndexPath) -> CGFloat {
        return UITableView.automaticDimension
    }
}

You can also use our default header cell AmityPostHeaderTableViewCell & default footer cell AmityPostFooterTableViewCell in your custom post component.

Step 3: Register your custom cell & implement datasource.

class YourViewController: UIViewController {
    
		func showFeed() {
				// 1.
				// Register your cell here. You can register both 
				// nib as well as class itself.
				AmityFeedUISettings.shared.register(UINib(nibName: "PostThumbsupTableViewCell", bundle: nil), forCellReuseIdentifier: "PostThumbsupTableViewCell")
        AmityFeedUISettings.shared.dataSource = self

        // Showing our feed UI
				let feedViewController = AmityGlobalFeedViewController.make()
	      navigationController?.pushViewController(feedViewController, animated: true)
		}
}

extension YourViewController: AmityFeedDataSource {
    
    // 2. 
    // Provide your rendering component for custom post.
    func getUIComponentForPost(post: AmityPostModel, at index: Int) -> AmityPostComposable? {
        switch post.dataType {
        case "your-data-type":
            return MyCustomPostComponent(post: post)
        default:
            return nil
        }
    }
}

Limitation

UIKit provides already built UI elements in one page. You can change the appearances, such as color and typography in the . However, UIKit does not allow you to replace these small components with other views. And you cannot modify the view hierarchy inside the page.

Custom Event Handler

There are many pages and actions on AmityUIKit. Pages can be nested inside others and it would be hard for overriding events on the nested pages. In order to solve this problem, we provide EkoEventHandler which is a behavior controller for actions that happen in UIKit.

Supported Events

Usage

UIKIT offers you a ready-to-use integration solution with the SDK Role & Permission feature. The default Community level role is Moderator.

Moderator badge

the "Moderator" badge shown on the post and the comment indicates it was created by a moderator user.

When a user clicks on the user profile avatar at the post creator area, UIKit will open

However, you can intercept the event and define your own logic following the example below.

Usage

To customize message cell layouts, please follow these instructions:

1. Create a subclass of UITableViewCell and conform it to AmityMessageCellProtocol

3. Subclass AmityEventHandler, and override its default functions channelDidTap(from:channelId:) and conform to AmityMessageListDataSource.

4. Assign a class instance through a set function of AmityUIKitManager

Customizing Cells with Different Layouts

Static-Height Cell Layout

You can use static-height cell layout types for static content, where the cell height is fixed and will not be scaled regardless of the data being received.

Below is an example of how you can configure a static-height cell layout. In this example, we're assuming that the image message is a class named StaticHeightMessageCell.

Dynamic-Height Cell Layout

You can use dynamic-height cell layout when you require your cell height to expand dynamically according to the data (e.g. label expands upon strings).

Dynamic-height cell layouts require more complexity in height calculation. Let's look at a text message as an example, where the height of the cell needs to expand dynamically to display the full content.