This page contains a checklist that you may consider as you decide to upgrade to the Experience Platform SDKs.
The Experience Platform SDK has experienced significant architectural re-design and comes with a major paradigm shift in terms of how customers may implement and leverage SDK functionality. The following checklist should help you understand some of these changes and what's required to move forward:
The new Experience Platform SDKs introduce the notion of a Mobile Core and constituent extensions. The Mobile Core contains core SDK functionality required for all implementations that require Adobe and/or third-party extensions.
Mobile Core and extensions are configured in Launch within a mobile property. When published, Launch hosts this property configuration and makes it for your SDK implementation.
You get to decide what SDK extensions to add, configure, and ultimately include in your app project - giving you the flexibility to customize your implementations. Note, however, certain extensions depend on others for proper functioning - these are documented where applicable.
We recommend easing your build process by leveraging dependency managers we support such as Gradle for Android and Cocoapods for iOS. Launch provides inline instructions and specs to help you with this process.
Begin with Getting Started section, ensure you are appropriately provisioned for Launch
Ensure all required SDK APIs you currently use are available in the new SDK (see AEP vs. 4x SDK )
Note that Experience Platform SDK supports iOS versions 10+, Android 4+ (API 14+)
If implementing Analytics, use Analytics processing rules to map variables/rules
Visit and ask questions on our community forum to get quick, thorough responses