There are several new features and benefits of using the new Adobe Experience Platform Mobile SDK. The new SDKs offer extensions to augment core SDK functionality, server-side configuration, and new Adobe Experience Cloud solution functionality. The table below highlights some of the improvements made in the new Adobe Experience Platform Mobile SDK.
| Core Features | AEP SDK | 4x SDK |
|---|---|---|
| Server-side, dynamic configuration | ✔️ | |
| Programmatic configuration | ✔️ | ✔️ |
| Configuration UI | Launch | Mobile Services |
| Partner SDK extensions | ✔️ | |
| Lifecycle metrics | ✔️ | ✔️ |
| GET/POST postbacks | ✔️ | ✔️ |
| Solution | AEP SDK | 4x SDK |
|---|---|---|
| Adobe Analytics | ✔️ | ✔️ |
| Adobe Analytics - Mobile Services | Messaging & Marketing Links | ✔️ |
| Adobe Audience Manager | ✔️ | ✔️ |
| Adobe Campaign Classic support | ✔️ | |
| Adobe Campaign Standard | Push & in-app messaging | Push only |
| Adobe Target | ✔️ | ✔️ |
| Adobe Target - Visual Experience Composer | ✔️ | ✔️ |
| (BETA) Adobe Experience Platform Location Service | ✔️ | |
| (BETA) Project Griffon Mobile Validation | ✔️ |
If you need access to Launch, see this page on User Permissions. If you have permissions to create a web property, you can create a mobile property. If you do not see the option to create a mobile property, turn off your ad blocker, and refresh the page.
If your apps send data to the same Analytics report suites, use the same extensions, rules, data elements, and so on, we recommend that you group all of these mobile apps into the same property. If your apps send data to different Analytics report suites, or user different extensions per app, and so on, we recommend that you create separate mobile properties. Alternatively, if you group your mobile apps into one property, split them into separate properties over time.
To delete a mobile property from Launch, see the bottom of Create a Property.
Warning: If you delete a mobile property, you cannot undo this action!
The Adobe Experience Platform SDK is available through Cocoapods and Gradle, and Github. For more information, see Get the SDK.
Implementing both SDKs is not recommended or supported.
The Experience Platform SDK migrates the locally stored user contexts from the 4x SDKs. Using both SDKs can cause severe data quality issues and user cliffing. For more information, see Upgrade to the Experience Platform SDKs.
| Extension | iOS (KB) | Android (KB) |
|---|---|---|
| Core | 504 | 168 |
| Adobe Analytics | 54 | 21 |
| Adobe Audience Manager | 40 | 13 |
| Adobe Target | 77 | 27 |
| Profile Framework | 20 | 8 |
The size values in the table are provided as indicative estimates, with the following considerations:
- Mobile Core, which includes Lifecycle, Identity, and Signals frameworks, is required for all other extensions. The final app size increase can be calculated by adding the Core size to each of the enabled extensions. For example, the iOS app distribution using Target and Analytics will have a total size increase of 635 KB. (Core: 504 KB + Analytics: 54 KB + Target: 77 KB).
- iOS (SDK extension versions 2+) estimates are based on Xcode’s App Thinning size report for one architecture. Android (SDK extension versions 1+) size estimates listed refer to unsigned apps and do not account for proguarding.
Android developer documentation recommends that to make "your APK file as small as possible, you should enable shrinking to remove unused code and resources in your release build". Shrinking is accomplished by using ProGuard.
The Adobe Experience Platform Mobile SDK for Android comes with default ProGuard rules included in the Core AAR package (see proguard.txt). Using this default package is the recommended path of implementation.
If you need to add the following rule to your custom ProGuard rules file - typically labeled as proguard-rules.pro. See Android developer documentation for more information.
-keep class com.adobe.marketing.mobile.* {
<init>(...);
}Lifecycle Metrics are "out-of-the-box" metrics that are automatically collected when the SDK is first implemented in your app. For more information, see Lifecycle.
For more information, see Processing Rules Tips and Tricks.
A launch is measured by the SDK when a user opens the app for the first time or returns to the app after having been out of the app for longer than the specified timeout value. The typical timeout is 5 minutes (300 seconds) in lifecycleTimeout configuration setting. A visit is a server-side calculation by Adobe Analytics and is based on the first and last data hits that are sent by the SDK without exceeding a visit timeout. Typically, session timeouts are set at 30 minutes for a report suite. Although visits come from traditional web analytics, these hits still provide valuable insights into how users enter and exit from your app.
Yes. To capture data in multiple report suites see Report Suites.