Customerly Mobile SDKs – New Implementation and Deprecation of Legacy Libraries

Raluca Stoica
Written by Raluca StoicaLast updated 2 days ago

1. Background and Rationale

Over the past years, Customerly has provided native SDKs for Android, iOS, and React Native to integrate the Customerly messenger into mobile applications.

The previous SDKs were developed in:

  • Kotlin for Android

  • Swift for iOS

  • JavaScript for React Native (which was only a wrapper around the Android and iOS SDKs)

While these SDKs allowed us to deliver the messenger experience natively, they introduced significant challenges in terms of maintainability:

  • Each SDK had to be maintained separately, in different languages and frameworks.

  • Feature parity across platforms required us to maintain three separate and highly complex projects, slowing down development and bug fixing.

  • Updates to the web messenger had to be manually mirrored across all SDKs, creating unnecessary duplication and delays.

To solve these issues and ensure long-term maintainability, scalability, and faster feature rollout, we are introducing a new generation of Customerly Mobile SDKs.

2. The New SDK Approach

The new SDKs are designed as a lightweight wrapper around the existing Customerly web messenger.

This approach allows us to:

  • Reuse the same core web messenger across all platforms.

  • Ensure feature parity by shipping updates simultaneously for web and mobile.

  • Greatly reduce complexity, since only the wrapper logic is maintained per platform.

  • Deliver a consistent experience to both app users and developers integrating the SDK.



If you want to see the SDK in action, you can download the Customerly mobile app and try the Support section, which runs on this new architecture.

3. Technical Details for Developers

While the new SDK simplifies implementation, there are a few important technical notes and limitations to be aware of:

  1. Chatflows

    • Chatflows triggered by “customer activity on the page” will not be evaluated in the mobile SDK environment.

    • Other chatflow triggers remain available.

  2. Notifications

    • Notifications generated by the web widget will be presented as native local notifications on the device.

    • Currently, local notifications are only shown when the app is open.

    • In the near future, we will enable developers to upload their push notification certificates (APNs / FCM) to deliver push notifications even when the app is closed or in the background.

  3. Implementation

    • Integration requires only a few lines of code to initialize the SDK and display the messenger when needed.

    • No deep native customization or maintenance is required on your side.

4. Deprecation of Legacy SDKs

With the release of the new SDKs, the previous versions of the Android, iOS, and React Native SDKs are officially deprecated.

  • The legacy SDKs have not been maintained for the past ~4 years.

  • Going forward, they will not receive any updates or fixes, not even for critical bugs.

  • We strongly encourage all developers to migrate to the new SDKs as soon as possible.

5. Support During Migration

We understand that migration requires adjustments on your side. Our team will be available to:

  • Provide clarifications on the new SDKs.

  • Offer support during the integration process.

  • Assist with best practices to ensure a smooth transition.

Please don’t hesitate to reach out to us if you have any questions while adopting the new SDKs.

Did this article help you solve your issue?

Customerly - Help Center

© 2025 Customerly - Help Center. All rights reserved.

Knowledge Base Software by Customerly