This blog post talks about how we migrated from Layer to Firebase in our existing chat application and what were the challenges we faced during this migration process. It will be quite helpful to mobile app developers while migrating the chat mobile apps or any existing apps with chat functionality. So, let’s look into the detailed process.

We had used Layer Android SDK for integrating chat functionality in one of our new-age messaging apps. This app has features like real-time 1 - 1 and group chatting, audio messages, recalling messages, Facebook messenger integration, payment gateway and military-grade security. The app is about 3-4 years old and is live on play store with a large number of paid users.

Layer provides SDK’s and API’s to implement real-time chat functionality in mobile applications.

It helps to implement real-time 1 - 1 chat and group-chat functionalities. Since, Layer had shut down on October 30th, 2019, we had to migrate our chat functionality on this messaging app to Firebase platform by migrating all old users’ data from Layer to Firebase.

Why we Migrated to Firebase?

The major reason behind migrating from Layer to Firebase is the shutdown of Layer Platform. To keep all the mobile apps with chat feature and chat apps that we developed running properly without any hassle, it was essential to migrate from Layer to another platform. So we chose one of the best platforms- Firebase.

Firebase provides two cloud-based database solutions that are client-accessible and support data syncing in real-time:

1) Cloud Firestore

2) Real-time Database

Cloud Firestore provides better scalability, and performance for web, mobile, and server development from the Firebase framework. It is a cloud-hosted NoSQL database. It can be directly accessed via native SDKs for iOS, Android, and web apps. It is also available in native Node.js, Python, Java, and Go SDKs, along with RPC-based and REST-based APIs.

Cloud Firestore can keep all your data in sync for different client apps with the use of real-time listeners. It can provide offline support for web and mobile for developing responsive apps that can work efficiently despite issues like internet connectivity or network latency.

Migration Steps we Followed:

1) Design Firestore Structure Model:

Cloud Firestore is a NoSQL database and it is document-oriented where the data can be stored in documents that are organized into collections. Each document contains a set of key-value pairs.

We designed the Firestore database structure as per our old data structure present on Layer.

2) Migrate Existing Data from Layer to Firebase:

To migrate chat data from Layer to Firebase, we created a script which helped to fetch data from Layer using Layer APIs and uploaded it to Firestore as per our data structure.

Layer provided data in JSON format and we converted that JSON format data to Collection and Document format.

3) Firebase SDK Integration and Development:

We integrated the Firebase Android SDK to work with Firestore. Then we implemented chat functionality for existing users and for new users as well.

List of Chat Functionalities we Implemented:

1) Basic Chatting Functionalities:

  • Text
  • Image
  • Video
  • Audio
  • Image with Text
  • Video with Text
  • Audio with Text chatting

2) Offline Chat Support

3) Message Features:

  • Search
  • Filter and Sorting
  • Clear All
  • Mark/Unmark
  • Delete

4) Message Settings:

  • Do not view messages older than a certain number of days
  • Automatically download photos and videos (Wifi only/Wifi and Mobile)
  • Automatically save received photos and videos to photo gallery
  • Set maximum video upload size

Challenges we Faced while Migrating from Layer to Firebase:

1) Designing a Proper Data Structure:

Designing a proper data structure in Firestore was a big challenge as we had to consider the smooth working of functionalities like search, sort, filter, unread message count and also ensure that data is stored in Collections and Documents.

2) Migrating Data from Layer to Firebase:

Converting JSON data retrieved from Layer to Firestore in Document and Collection format was one of the challenges we faced. Also, the size of Layer data was quite big which consisted of text, audios, images, and videos. We did this step-by-step by first migrating data of most active users and subsequently all other users.

3) Syncing data from Firestore to Android App Local Database:

Another challenge we faced was about syncing the migrated data from Firestore to the local Android app for both online and offline support, especially when the user opens the app for the first time after migration. Here in some cases where the size of users’ conversation was large, it took quite a bit of time to sync the data.

Hence to overcome this issue, we synced first just the conversation list and after opening actual conversation, synced messages within that conversation.

The Bottom Line:

Due to Layer shutdown, many applications had faced issues with their chat functionality and hence it was necessary to migrate their implementation from Layer to any other platform. As a prominent mobile app development company, Biz4Solutions has good experience not only in chat application development, but also in migrating the chat functionality of existing apps from Layer to a robust platform like Firebase.

So, do you also want to migrate any of your applications from Layer to Firebase? Reach out to us today! We have a team of highly skilled mobile app developers and technical experts trained for solving various critical software solutions.

Author's Bio: 

Shelly Megan is a Project Manager at Biz4Solutions with 14+ years of experience in Project Management, Quality Assurance and Test Management in IT-related services. She has expertise in various domains like Healthcare, Finance, Water technologies, Transportation, Telecom, etc. She has experience in defining and implementing quality management strategies to ensure exceptional delivery of software projects.