/chat-sdk-android

Chat SDK Android - Open Source Mobile Messenger

Primary LanguageJavaOtherNOASSERTION

Chat SDK for Android

Open Source Messaging framework for Android

Chat SDK is a fully featured open source instant messaging framework for Android. Chat SDK is fully featured, scalable and flexible and follows the following key principles:

  • Free. The Chat SDK is free for commercial use
  • Open Source. The Chat SDK is open source
  • Full control of the data. You have full and exclusive access to the user's chat data
  • Quick integration. Chat SDK is fully featured out of the box
  • Demo Versions. Firebase or XMPP open this link on your Android phone to install
  • Scalable. Supports millons of daily users [1, 2]
  • Backend agnostic. Chat SDK can be customized to support any backend

Technical details

  • Multiple backend support Firebase, ejabberd, OpenFire
  • Data storage all data is persisted using the GreenDao
  • Dynamic image loading using Fresco
  • Reactive using RXAndroid
  • Java 8 supports Java 8 and lamda expressions
  • API Level 16+ Compatible with 99.3% of Android devices

Features

  • Private and group messages
  • Public chat rooms
  • Username / password, Facebook, Twitter, Anonymous and custom login
  • Phone number authentication
  • Push notifications (using FCM)
  • Text, Image and Location messages
  • User profiles
  • User search
  • Powered by Firebase
  • Firebase UI
  • iOS Version
  • Web Version

Performance and Scalability

These are the average Firebase hosting costs calculated using the Firebase Database Profiling tool. Firebase charge 1 USD per GB of data downloaded (excluding images or files). We've tabulated a few common operations and how many of them can be performed per 1 USD of monthly hosting cost:

  • Messages Received (1kb) = 1,000,000
  • Logins (10kb) = 100,000
  • Profile Update (0.2kb) = 5,000,000
  • User search (2kb) = 500,000

What's possible on the Firebase free plan (10GB / month):

500k logins, 5 million messages.

What's possible on the Flame plan (20GB / month / 20 USD):

1 million logins, 10 million messages.

The real-time database will support up to 100k concurrent users. From our experience, 1 concurrent connection is enough to support 10 users per minute. That means that at peak capacity, the Chat SDK could support 1 million users per minute and well over 20 million monthly users.

Modules

The Chat SDK has a number of additional modules that can easily be installed including:

Firebase Firestore

If you are interested in a version of the Chat SDK that supports Firebase's new database please vote on this issue and help us meet our target on Patreon.

Support the project

We would love to work full time developing the open source. At the moment we have to spend a substantial amount of time doing other consulting work to cover our costs. If you like what we're doing and would like to support us to focus more of our time on the open source project we would be very grateful.

Get involved!

We're very excited about the project and we're looking for other people to get involved. Over time we would like to make the best messaging framework for mobile. Helping us could involve any of the following:

  • Providing feedback and feature requests
  • Reporting bugs
  • Fixing bugs
  • Writing documentation
  • Improving the user interface
  • Help us update the library to use Swift
  • Helping to write adapters for other services such as Layer, Pusher, Pubnub etc...
  • Write a tutorial - we pay $100 for quality tutorials

If you're interested please review the Contributing Document for details of our development flow and the CLA then email me at team@chatsdk.co.

Apps that use Chat SDK

If you have an app that uses the Chat SDK let us know and we'll add a link.

Running the demo project

This repository contains a fully functional version of the Chat SDK which is configured using our Firebase account and social media logins. This is great way to test the features of the Chat SDK before you start integrating it with your app.

Note: You should make sure that the correct SDK versions and build tools are installed in Android Studio. To do this open the Preferences panel and navigate to Appearance & Behavour -> System Settings -> Android SDK or click on the SDK Manager icon in the tool bar. Android SDK versions 8.1 and onwards should be installed. Android SDK Build-Tools version that is defined in the gradle.properties file under the ANDROID_BUILD_TOOLS_VERSION property.

The next step is to setup the Chat SDK using your Firebase and Social Accounts. To do that continue here.

Setup Service

We provide extensive documentation on Github but if you’re a non-technical user or want to save yourself some work you can take advantage of our setup and integration service.

Adding the Chat SDK to your project

Quick start guide - it takes about 10 minutes!

Integration with an existing project is simple. You can add the core libraries using Gradle.

Gradle

Until the project is published in jCenter, you will need to include the repository manually:

repositories {
    maven { url "http://dl.bintray.com/chat-sdk/chat-sdk-android" }
    maven { url "https://maven.google.com" }
    maven { url "https://jitpack.io" }
}

Then add this to your dependencies area:

compile 'co.chatsdk.chatsdk:chat-sdk-core:4.6.0'
compile 'co.chatsdk.chatsdk:chat-sdk-ui:4.6.0'
compile 'co.chatsdk.chatsdk:chat-sdk-firebase-adapter:4.6.0'
compile 'co.chatsdk.chatsdk:chat-sdk-firebase-file-storage:4.6.0'

You may also need to enable Java 8:

compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

You can also add the modules manually by downloading source code and importing the modules to Android Studio.

Firebase depends on Google Services so we need to apply the google services plugin. This will read the Google Services file that we will add during Firebase setup. Add this to your top level build.gradle file.

buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.google.gms:google-services:4.0.1'
    }
}

Add this to the end of your app level build.gradle file:

apply plugin: 'com.google.gms.google-services'

Android X

Make sure you've added the following to your gradle.properties file:

android.useAndroidX=true
android.enableJetifier=true

Initializing the Chat SDK

Now open your applications's main class and find the onCreate method. Add the following to setup the Chat SDK:

Context context = getApplicationContext();

// Create a new configuration
Configuration.Builder builder = new Configuration.Builder(context);

// Perform any configuration steps (optional)
builder.firebaseRootPath("prod");

// Initialize the Chat SDK
try {
     ChatSDK.initialize(builder.build(), new FirebaseNetworkAdapter(), new BaseInterfaceAdapter(context));
}
    catch (ChatSDKException e) {
}

// File storage is needed for profile image upload and image messages
FirebaseFileStorageModule.activate();
FirebasePushModule.activate();

// Activate any other modules you need.
// ...

Activate the core Chat SDK modules and any other modules you need. See the module setup guide for more information.

Launch the Chat SDK login activity by adding this to your AndroidManifest.xml:

<activity android:name="co.chatsdk.ui.login.LoginActivity">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
</activity>

Or if you want to launch the activity manually, you can do it using:

InterfaceManager.shared().a.startLoginActivity(context, true);

Firebase Setup

  1. Go to the Firebase website and sign up or log in
  2. Go to the Firebase console and make a new project
  3. Click Add project
  4. Choose a name and a location
  5. Click Settings (the gear icon). On the General tab, click Add App -> Add Firebase to your Android app
  6. Enter your package name - found in your app's build.gradle file, app name and SHA-1 key (optional)
  7. Download the google-services.json file and add it to your app project. It should be added inside the app folder.
  8. Set a custom root path. The chat SDK allows you to run multiple chat instances on one Firebase database. This could be useful if you want test and production environments for example. To do this set builder.firebaseRootPath("prod") in the configuration builder.
  9. In the Firebase dashboard click Authentication -> Sign-in method and enable all the appropriate methods

Enabling location messages

The Chat SDK needs two google services to support location messages. The Google Places API to select the location and the Google Static Maps API to display the location.

Add the following during the configuration stage:

builder.googleMaps("YOUR GOOGLE MAPS STATIC API KEY");

You will also need to add your Google Places API key to the app manifest:

<meta-data android:name="com.google.android.geo.API_KEY" android:value="YOUR GOOGLE PLACES API KEY"/>

Note: You need to enable billing in your google cloud console or else you will not be able to view map images in your messages, For more information visit the Google usage and billing support page

You can disable location messages using the builder.locationMessagesEnabled(false) option.

Conclusion

Congratulations! 🎉🎉 You've just turned your app into a fully featured instant messenger! Keep reading below to learn how to further customize the Chat SDK.

Next Steps

Check out the Development Guide

We've written a comprehensive Development Guide which is available in the docs repository.

If you thing that something is missing, you can post a new issue and we will update the guide.

We have a number of additional guides available on our Wiki.

Configuration

The Chat SDK can be customized during setup using the configuration builder object. For a full list of options, take a look at here.

Configuration using the Configuration Builder

In your main onCreate method you create a new instance of the Configuration.Builder and pass it to the ChatSDK singleton on initialization.

Here you have the option to set far more properties. For example:

Disable Facebook and Twitter login
builder.facebookLoginEnabled(false);
builder.twitterLoginEnabled(false);
Set a custom user name and avatar
builder.defaultUserName("TestUser");
builder.defaultUserAvatarUrl("http://your-site/image.png");

Remember that in the instructions we will advise you to configure using the Android Manifest but you are always free to use the direct configuration method instead.

Module Setup

There are a number of free and premium extensions that can be added to the Chat SDK.

Firebase Modules

For the following modules:

The free modules are located in the main Github repository. The premium modules can be purchased and downloaded from the links provided above.

Push Notifications

Add the following to your build.gradle

Add the library

Gradle

compile 'co.chatsdk.chatsdk:chat-sdk-firebase-push:4.6.0'

Manual Import

compile project(path: ':chat-sdk-firebase-push')
Enable the module

In your main class onCreate method add:

FirebasePushModule.activate();
Setup Firebase Cloud Functions

To handle push notifications, we use Firebase Cloud Functions. This service allows you to upload a script to Firebase hosting. This script monitors the realtime database and whenever a new messsage is detected, it sends a push notification to the recipient.

Below is a summary of the steps that are required to setup push using the Firebase Cloud Functions script. For further instructions you can look at the Firebase Documentation.

  1. Run firebase login and login using the browser
  2. Make a new directory to store your push functions in. It can be called anything
  3. Navigate to that directory using the terminal
  4. Run firebase init functions
  5. Choose the correct app from the list
  6. Choose JavaScript
  7. Choose y for ESLint
  8. Choose Y to install node dependencies
  9. Find the functions directory you've just created and copy the index.js file from Github into the directory
  10. Run firebase deploy

Now the script is active and push notifications will be set out automatically.

Firebase UI

Add the library

Add the following to your build.gradle

compile 'co.chatsdk.chatsdk:chat-sdk-firebase-ui:4.6.0'
Enable the module

Add the following to the end of your onCreate method:

FirebaseUIModule.activate(context, GoogleAuthProvider.PROVIDER_ID, PhoneAuthProvider.PROVIDER_ID);

Add this to your AndroidManifest.xml

<activity android:name="co.chatsdk.firebase.ui.FirebaseUIActivity">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
</activity>

To specify your own splash screen, you need to make a subclass of the SplashScrenActivity. Then call:

FirebaseUIModule.shared().setSplashScreen([your subclass]);

Also make sure to update the Android Manifest with this class too.

You can provide a list of providers as outlined in the Firebase documentation.

Note You will need to remove the com.facebook.sdk.ApplicationId meta data from the app manifest or you will get a Gradle build error.

Social Login

Add the following to your build.gradle

Add the library

Gradle

compile 'co.chatsdk.chatsdk:chat-sdk-firebase-social-login:4.6.0'

Manual Import

compile project(path: ':chat-sdk-firebase-social-login')
Enable the module

In your main class onCreate method add:

FirebaseSocialLoginModule.activate(getApplicationContext());

Facebook

  1. On the Facebook developer site get the App ID and App Secret
  2. Go to the Firebase Console and open the Auth section
  3. On the Sign in method tab, enable the Facebook sign-in method and specify the App ID and App Secret you got from Facebook.
  4. Then, make sure your OAuth redirect URI (e.g. my-app-12345.firebaseapp.com/__/auth/handler) is listed as one of your OAuth redirect URIs in your Facebook app's settings page on the Facebook for Developers site in the Product Settings > Facebook Login config
  5. Add the following to your AndroidManifest.xml:
<meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_identifier"/>

Add the following to your chat_sdk_firebase.xml file:

<string name="facebook_app_identifier">[FACEBOOK APP KEY]</string>
  1. Go back to the Facebook site and click "Add Platform". Choose Android and enter your Bundle ID. Then you will need to enter add the Key Hashes property. To do this first generate a key store for your app. Then generate the hash by running the following on MacOS:
keytool -exportcert -alias <RELEASE_KEY_ALIAS> -keystore <RELEASE_KEY_PATH> | openssl sha1 -  binary | openssl base64

On Windows, use:

keytool -exportcert -alias <RELEASE_KEY_ALIAS> -keystore <RELEASE_KEY_PATH> | openssl sha1 -binary | openssl base64

Twitter

  1. Register your app as a developer application on Twitter and get your app's API Key and API Secret.
  2. In the Firebase console, open the Auth section.
  3. On the Sign in method tab, enable the Twitter sign-in method and specify the API Key and API Secret you got from Twitter.
  4. Then, make sure your Firebase OAuth redirect URI (e.g. my-app-12345.firebaseapp.com/__/auth/handler) is set as your Callback URL in your app's settings page on your Twitter app's config.
  5. Add the following to your AndroidManifest.xml:
<meta-data android:name="twitter_key" android:value="@string/twitter_key" />
<meta-data android:name="twitter_secret" android:value="@string/twitter_secret" />

Add the following to your chat_sdk_firebase.xml file:

<string name="twitter_key">[TWITTER KEY]</string>
<string name="twitter_secret">[TWITTER SECRET]</string>

Google

  1. If you haven't yet specified your app's SHA-1 fingerprint, do so from the Settings page of the Firebase console. See Authenticating Your Client for details on how to get your app's SHA-1 fingerprint.
keytool -exportcert -alias [KEY ALIAS] -keystore [PATH/TO/KEYSTORE] -list -v

Note: You may need to add multiple keys for debug and release

  1. In the Firebase console, open the Auth section.
  2. On the Sign in method tab, enable the Google sign-in method and click Save.
  3. You must pass your server's client ID to the requestIdToken method. To find the OAuth 2.0 client ID.
  4. Open the Credentials page in the API Console.
  5. The Web application type client ID is your backend server's OAuth 2.0 client ID.
  6. Add the following to your AndroidManifest.xml:
<meta-data android:name="google_web_client_id" android:value="@string/google_web_client_id" />

Add the following to your chat_sdk_firebase.xml file:

<string name="google_web_client_id">[CLIENT ID]</string>

Social login can also be enabled or disabled by changing the Chat SDK configuration.

Other Modules

For the following modules:

After you have purchased the module you will be provided with a link to the module source code. Unzip this file and import it into Android Studio.

  1. Click File -> New -> Import Module
  2. Add the module to your build.gradle
compile project(path: ':chat_sdk_[module name]')
  1. Sync Gradle
  2. In your main class onCreate activate the module:
ContactBookModule.activate();

Security Rules

Firebase secures your data by allowing you to write rules to govern who can access the database and what can be written. On the Firebase dashboard click Database then the Rules tab.

Copy the contents of the rules.json file into the rules and click publish.

Adding Modules Manually

In Android Studio:

File -> New -> Import Module

You must import the following core module:

  • chat-sdk-ui

And at least one network adapter:

And any of the following optional modules:

Now import the modules in your build.gradle file.

compile project(path: ':chat-sdk-ui')
compile project(path: ':chat-sdk-firebase-push')

If you want to import modules manually, you should add the following to your gradle.properties file:

useLocal=true

You will also need to make sure that you've included the library versions in your main project level build.gradle file by adding the following:

ext {
    bintrayVersion = "1.8.4"
    mavenGradleVersion = "2.1"
    androidxAppcompatVersion = "1.0.2"
    androidxConstraintLayoutVersion = "2.0.0-alpha2"
    androidxLifecycleExtensionsVersion = "2.0.0"
    androidxRecyclerViewVersion = "1.0.0"
    materialVersion = "1.0.0"
    playAuthVersion = "16.0.1"
    playMapsVersion = "16.0.0"
    playPlacesVersion = "16.0.0"
    firebaseUiVersion = "4.2.1"
    firebaseCoreVersion = "16.0.5"
    firebaseDatabaseVersion = "16.0.5"
    firebaseAuthVersion = "16.0.5"
    firebaseStorageVersion = "16.0.5"
    firebaseMessagingVersion = "17.3.4"
    firebaseFunctionsVersion = "16.1.3"
    timberVersion = "4.7.1"
    greenDaoVersion = "3.2.2"
    frescoVersion = "1.10.0"
    rxJavaVersion = "2.2.3"
    rxAndroidVersion = "2.1.0"
    gsonVersion = "2.8.5"
    jodaTimeVersion = "2.10.1"
    apacheCommonsVersion = "3.7"
    compressorVersion = "2.1.0"
    okHttpVersion = "3.11.0"
    facebookLoginVersion = "4.34.0"
    twitterVersion = "3.3.0"
    prettyTimeVersion = "4.0.1.Final"
    countryPickerVersion = "2.0.0"
    imageCropperVersion = "2.8.0"
    photoViewVersion = "2.2.0"
}

This will prompt the modules to use local versions of the core Chat SDK modules rather than the versions hosted on Gradle.

Configuring the project

Now that the modules have been added, we need to configure the project.

SDK Version

Now you will see that gradle cannot be sync because it missing some parameters. Open to gradle.properties file in the root of the project and make sure the following lines are set to the latest values.

MIN_SDK = 16
ANDROID_BUILD_TARGET_SDK_VERSION = 25
ANDROID_COMPILE_SDK_VERSION = 28
ANDROID_SUPPORT_VERSION = 28.0.0

Note: You should make sure that the correct SDK versions and build tools are installed in Android Studio. To do this open the Preferences panel and navigate to Appearance & Behavior -> System Settings -> Android SDK or click on the SDK Manager icon in the tool bar. Android SDK versions 4.4 and onwards should be installed. Android SDK Build-Tools version 21.1.0 should be installed.

Add any other modules that you need. Then sync the project with gradle.

Backend agnostic architecture

The user interface for the Chat SDK is completely decoupled from the backend. This means that the Chat SDK can be adapted to connect to any type of messaging server by creating a custom network adapter. Currently we have written two network adapters, one for Firebase and another for XMPP. This has a number of benefits:

  1. You can connect the Chat SDK user interface to your messaging server by writing a custom network adapter. This saves you the complex job of building a full user interface.

  2. You can switch the backend your app uses. Imagine that you decide to start off with the Firebase version of the Chat SDK but at some point you decide that you want to switch to using an XMPP server. Usually, this would require a full rewrite of the messaging client but with the Chat SDK it can be achieved by changing one line of code!

If you want more details about writing a custom network adapter you can email us at team@chatsdk.co.

The license

We offer a choice of two license for this app. You can either use the Chat SDK license or the GPLv3 license.

Most Chat SDK users either want to add the Chat SDK to an app that will be released to the App Store or they want to use the Chat SDK in a project for their client. The Chat SDK license gives you complete flexibility to do this for free.

Chat SDK License Summary

  • License does not expire.
  • Can be used for creating unlimited applications
  • Can be distributed in binary or object form only
  • Commercial use allowed
  • Can modify source-code but cannot distribute modifications (derivative works)

If a user wants to distribute the Chat SDK source code, we feel that any additions or modifications they make to the code should be contributed back to the project. The GPLv3 license ensures that if source code is distributed, it must remain open source and available to the community.

GPLv3 License Summary

  • Can modify and distribute source code
  • Commerical use allowed
  • Cannot sublicense or hold liable
  • Must include original license
  • Must disclose source

What does this mean?

Please check out the Licensing FAQ for more information.