stream_chat_flutter 0.2.0-alpha+1 stream_chat_flutter: ^0.2.0-alpha+1 copied to clipboard
Stream Chat official Flutter SDK. Build your own chat experience using Dart and Flutter.
Flutter Chat Components #
The official Flutter components for Stream Chat, a service for building chat applications.
Quick Links
- Register to get an API key for Stream Chat
- Flutter Chat Tutorial
- Chat UI Kit
Flutter Chat Tutorial #
The best place to start is the Flutter Chat Tutorial. It teaches you how to use this SDK and also shows how to make common changes.
Example App #
This repo includes a fully functional example app with setup instructions. The example is available under the example folder.
Add dependency #
dependencies:
stream_chat_flutter: ^0.1.19
You should then run flutter packages get
Alpha version #
Use version ^0.2.0-alpha+1
to use the latest available version.
Note that this is still an alpha version. There may be some bugs and the api can change in breaking ways.
Thanks to whoever tries these versions and reports bugs or suggestions.
Android #
All set ✅
iOS #
The library uses flutter file picker plugin to pick files from the os. Follow this wiki to fulfill iOS requirements.
We also use video_player to reproduce videos. Follow this guide to fulfill the requirements.
To pick images from the camera we use the image_picker plugin. Follow these instructions to check the requirements.
Docs #
Business logic components #
We provide 2 Widgets dedicated to business logic and state management:
UI Components #
These are the available Widgets that you can use to build your application UI.
Every widget uses the StreamChat
or StreamChannel
widgets to manage the state and communicate with Stream services.
- ChannelHeader
- ChannelImage
- ChannelListView
- ChannelName
- ChannelPreview
- MessageInput
- MessageListView
- MessageWidget
- StreamChatTheme
- ThreadHeader
Customizing styles #
The Flutter SDK comes with a fully designed set of widgets which you can customize to fit with your application style and typography.
Changing the theme of Chat widgets works in a very similar way that MaterialApp
and Theme
do.
Out of the box all chat widgets use their own default styling, there are two ways to change the styling:
- Initialize the
StreamChatTheme
from your existingMaterialApp
style
class MyApp extends StatelessWidget {
final Client client;
MyApp(this.client);
@override
Widget build(BuildContext context) {
final theme = ThemeData(
primarySwatch: Colors.green,
);
return MaterialApp(
theme: theme,
home: Container(
child: StreamChat(
streamChatThemeData: StreamChatThemeData.fromTheme(theme),
client: client,
child: ChannelListPage(),
),
),
);
}
}
- Construct a custom theme and provide all the customizations needed
class MyApp extends StatelessWidget {
final Client client;
MyApp(this.client);
@override
Widget build(BuildContext context) {
final theme = ThemeData(
primarySwatch: Colors.green,
);
return MaterialApp(
theme: theme,
home: Container(
child: StreamChat(
streamChatThemeData: StreamChatThemeData.fromTheme(theme).copyWith(
ownMessageTheme: MessageTheme(
messageBackgroundColor: Colors.black,
messageText: TextStyle(
color: Colors.white,
),
avatarTheme: AvatarTheme(
borderRadius: BorderRadius.circular(8),
),
),
),
client: client,
child: ChannelListPage(),
),
),
);
}
}
Offline storage #
By default the library saves information about channels and messages in a SQLite DB.
Set the property persistenceEnabled
to false if you don't want to use the offline storage.
Push notifications #
To enable push notifications set the property pushNotificationsEnabled
to true
.
Android
Follow the guide at this link to setup Firebase for Android.
Set the notification template on your GetStream dashboard to be like this:
template = {}
data template = {
"message_id": "{{ message.id }}"
}
Create a Application.kt file to be like this:
class Application : FlutterApplication(), PluginRegistrantCallback {
override fun onCreate() {
super.onCreate()
FlutterFirebaseMessagingService.setPluginRegistrant(this)
}
override fun registerWith(registry: PluginRegistry?) {
PathProviderPlugin.registerWith(registry?.registrarFor(
"io.flutter.plugins.pathprovider.PathProviderPlugin"))
SharedPreferencesPlugin.registerWith(registry?.registrarFor(
"io.flutter.plugins.sharedpreferences.SharedPreferencesPlugin"))
FlutterLocalNotificationsPlugin.registerWith(registry?.registrarFor(
"com.dexterous.flutterlocalnotifications.FlutterLocalNotificationsPlugin"))
FirebaseMessagingPlugin.registerWith(registry?.registrarFor("io.flutter.plugins.firebasemessaging.FirebaseMessagingPlugin"))
}
}
Update the AndroidManifest.xml
file to set the application class:
...
<uses-permission android:name="android.permission.INTERNET"/>
<application
android:name=".Application"
android:label="example"
android:icon="@mipmap/ic_launcher">
<activity
android:name=".MainActivity"
android:launchMode="singleTop"
...
iOS
Make sure you have correctly configured your app to support push notifications, and that you have generated certificate/token for sending pushes.
Offline support for push notifications
- open the XCode project
- create a new target of type
Notification service extension
- add
App Groups
capability to theRunner
target and the just created one - add the line
pod 'StreamChatClient', :git => 'https://github.com/GetStream/stream-chat-swift.git', :branch => 'release/2.0'
to the Podfile - run
pod install
- substitute the code in the
Notification service
with this one and substitute APPGROUP with the just created one - do the same with
AppDelegate.swift
using this template - set the notification template on your GetStream dashboard to be like this:
template = {
"aps" : {
"alert" : {
"title" : "{{ sender.name }} @ {{ channel.name }}",
"body" : "{{ message.text }}"
},
"badge": {{ unread_count }},
"apns-priority": 10,
"mutable-content" : 1
},
"message_id": "{{ message.id }}"
}
Of course you can change the alert
object as you want. Just make sure it has the last three lines.
Contributing #
We welcome code changes that improve this library or fix a problem, please make sure to follow all best practices and add tests if applicable before submitting a Pull Request on Github. We are very happy to merge your code in the official repository. Make sure to sign our Contributor License Agreement (CLA) first. See our license file for more details.