1.5.0

Release of version 1.5.0

What's Changed

• prepare release 1.4.3 by @wenxi-zeng in #72
• Capture Destination Metadata by @prayansh in #73
• support destination clean up by @wenxi-zeng in #74
• add versioned plugin by @wenxi-zeng in #75

Full Changelog: 1.4.3...1.5.0

1.4.3

Release of version 1.4.3

What's Changed

• prepare release 1.4.2 by @wenxi-zeng in #69
• fix ANR caused by DRM api by @wenxi-zeng in #71

Full Changelog: 1.4.2...1.4.3

1.4.2

Release of version 1.4.2

What's Changed

• prepare release 1.4.1 by @wenxi-zeng in #64
• fix useLifecycleObserver not trigger lifecycle events issue by @wenxi-zeng in #65
• Integrations Logic fix + Copy mechanism for payloads by @prayansh in #59
• prevent using jvm initializer in android and address violation of retrieving unsettable device id by @wenxi-zeng in #67
• Fix the enable logic for destinations by @prayansh in #68

Full Changelog: 1.2.0...1.4.2

1.4.1

What's Changed

• Beta Release README update by @prayansh in #35
• prepare for release 1.3.0 by @wenxi-zeng in #37
• Fix destination processing logic by @prayansh in #39
• increase test coverage by @wenxi-zeng in #38
• Wenxi/intercom destination by @wenxi-zeng in #40
• Wenxi/change amplitude session plugin key by @wenxi-zeng in #41
• Mixpanel + Firebase Refactor by @prayansh in #43
• Add sample appsflyer destination plugin by @prayansh in #44
• Add sample comscore destination plugin by @prayansh in #45
• remove intercom test smell code by @wenxi-zeng in #47
• Documentation Improvements by @prayansh in #48
• Wenxi/suspendable analytics by @wenxi-zeng in #50
• setup github actions by @wenxi-zeng in #52
• Wenxi/replace flush upload with channel api by @wenxi-zeng in #53
• add cancel previous by @wenxi-zeng in #54
• Migs647/logger by @migs647 in #56
• Wenxi/fix identity doc by @wenxi-zeng in #57
• upgrade firebase cloud messaging by @wenxi-zeng in #58
• Wenxi/convenience methods and misses for plugin authors by @wenxi-zeng in #60
• readme enhancements by @wenxi-zeng in #61
• automated release by @wenxi-zeng in #62

Full Changelog: 1.3.0...1.4.1

1.3.0

Changelog

• remove analytics reference from AndroidStorage (#25)
• LIBMOBILE-338 add update type param to update (#26)
• fix naming (#27)
• Json Utility improvements & Re-add Alias Event (#29)
• LIBMOBILE-529 java compatibility (#30)
• make storage weak (#31)
• SegmentDestination refactor and add cdnHost config option (#34)
• keep dispatcher and scope config internal (#36)

1.2.0

• Updated to latest firebase analytics for destination (#17)
• add new helpers for destinations (#18)
• add consumer proguard rules (#21)
• Refactor plugin interface and update apis (#19)
• Add a base64 encoding implementation (#23)
• Add new mapTransform function (#24)

1.1.1

Jun 30 2021

• Update Jitpack configs

1.1.0

Jun 30 2021

• Added a Startup Queue plugin
• Refactored modules to support JVM as a first-class platform
• Sample app changes
• Added example for push notification tracking
• Added Firebase, Mixpanel and Amplitude device-mode destination plugins as examples

1.0.0 (Pilot Release)

Analytics-Kotlin v1.0.0

We are announcing the pilot of Analytics Kotlin! Analytics Kotlin is a library that provide a simple, modern instrumentation experience for mobile apps.

Why did we launch Analytics Kotlin?

The Android ecosystem has evolved rapidly, and has introduced new frameworks and best practices for building and managing mobile apps. To align with some significant advancements in these ecosystems over the last few years, we are introducing Analytics Kotlin library.

What do you need to know about Analytics Kotlin?

Analytics Kotlin library improves performance, data observability, and the overall developer experience. Additionally, the improved app performance unlocks insights into app funnel and business metrics with a modern developer experience. The library opens opportunities to instrument app tracking across platforms.

Are there any known limitations to Analytics Kotlin?

Analytics Kotlin does not support mobile device-mode destinations. Destinations may only be configured in cloud mode during pilot.

Should these library be used in production?

During the pilot phase, we strongly discourage production use cases. This library is prone to change and we may introduce breaking changes. This library is governed under our First-Access & Beta terms.