Should I migrate to the new mobile SDKs?

The former SDKs have been deprecated since August 2023. While migration is not mandatory, it is strongly recommended to benefit from continued support, bug fixes, and new features.

What does "deprecated" mean?

Since August 2023, the former SDKs are no longer officially maintained. This means:

🚫 No bug fixes — any existing or future bugs will not be corrected
🚫 No new features — no further development will be done on the former SDKs
⚠️ Very limited support — our teams can only provide minimal assistance for issues related to the former SDKs

What are the benefits of the new SDKs?

The new SDKs bring significant improvements:

Flexible event-based tagging — you can attach any property to any event, giving you much greater freedom in your tagging plan. The former SDKs are rigid in their methods and do not allow this level of customization.
Cleaner, more readable code — the new SDK offers a much more transparent codebase, making it easier for your own technical teams to read, understand, and debug the implementation independently.

➡️ New Android (Java) SDK
➡️ New Android (Kotlin) SDK
➡️ New iOS (Swift) SDK
➡️ New Flutter SDK

Am I forced to migrate?

No, migration is not mandatory. If your current tagging plan works as expected and you do not plan to make any changes or additions in the future, the immediate benefits of migrating are admittedly limited. However, please keep in mind the risks of staying on a deprecated SDK.

Important: If you ever encounter a bug, need a new feature, or require support assistance, we will not be able to help you on the former SDKs. By choosing not to migrate, you accept this risk. We strongly recommend planning a migration to avoid being in a difficult situation should any issue arise in the future.