Take a tour of new features and capabilities of Adobe Experience Platform Launch that will help manage Adobe Experience Platform Mobile SDK to accelerate mobile application development.
Giving your users a great mobile experience means constantly evaluating how they are interacting with your app and quickly responding with updates and optimizations. Based on these guiding principles, we builtAdobe Experience Platform Mobile SDKfrom the ground-up to be modular, flexible and dynamic. Managing mobile SDKs throughAdobe Experience Platform Launchbrings a host of new features and capabilities that enable you to better engage with your users with meaningful personalization.
Let’s take a look at some of the top features of the Adobe Experience Platform Mobile SDKs and how managing them with Launch can accelerate your mobile application development.
Adobe Experience Platform Mobile SDK can be implemented across a variety of platforms. For Android and iOS, we use dependency managers (CocoaPodsandGradle) to ensure that we pull the correct versions of the extensions and any necessary dependent files. We also support additional platforms such asReact Native,FlutterandWeChat Mini Programs. Soon, we will have support forApache Cordova,Xamarin, andUnity.
Easily Activate Adobe Experience Cloud solutions in Launch
Thousands of companies and organizations already use Adobe Experience Platform Launch for website tag management and configuration. For mobile, Launch lets you create and manage mobile properties providing a familiar set of controls and workflow paradigms for managing app implementations. Getting started with Launch’s mobile workflows is easy. ActivatingLaunchfor mobile applications does not require its use on your website or vice versa (Figure 1).
Figure 1: The user interface in Adobe Experience Platform Launch now allows the user to select mobile applications as an option for creating a new property.
When you develop your application with the Adobe Experience Platform Mobile SDK, you retain a dynamic link back to your Adobe Experience Platform Launch property. Keeping this live link allows you to push configuration and resource updates to your application dynamically without requiring a developer to rebuild or resubmit a new version of the app each time.
Think about how many times you wished you had the ability to change anAdobe Analyticsreport suite or anAdobe Targetclient code but decided not to because it would require you to resubmit your application.
Launchalso provides a publishing process that allows you to phase-gate your changes, first testing in development, staging and finally production (Figure 2).
Figure 2: Publishing workflow queues in Adobe Experience Platform Launch.
TheMobile Core event hublies at the heart of the Adobe Experience Platform Mobile SDK. The Mobile Core event hub provides the core data structure tied to all SDK extensions, maintaining a list of registered extensions and internal modules, a list of registered event listeners, and a shared state database.
The event hub publishes and receives event data from registered extensions to simplify integrations with Adobe and third-party solutions. Customers can also build private extensions to connect with internal business systems that they wish to integrate into mobile workflows.
Figure 3: Extension architecture for Experience Platform Mobile SDK.
Data elements in Adobe Experience Platform Launch act as aliases, making it easier to access data flowing through your mobile SDK implementation from both Adobe solutions and third-party extensions. Using data elements, customers can easily reference or use data as a workflow trigger, or condition. Data elements also make it easy to include mobile data such as context data, IDs, or anything else in post-backs to external endpoints (Figure 4).
Figure 4: Example of a data element in Adobe Experience Platform Launch.
One of the main benefits of using Adobe Experience Platform Launch to manage your mobile SDK implementation is the ability to create both simple and complex workflow rules. You can define what events and or conditions you want to trigger an action and then deploy these new rules to your application dynamically. Because your application maintains a live-link to your Launch environments you can easily add or modify rules depending on your needs.
Figure 5: Example of a workflow rule based on location entry.
The icing on the cake is a brand new data and experience validation tool called “Project Griffon.” With Project Griffon, mobile app developers, product owners and marketers alike can easily understand how data is flowing through app implementations and how it is processed through Adobe Analytics.
With no need to create proxy networks, install profiles or certificates, Project Griffon accelerates mobile application development by creating a secure session through a QR code or deep-link that allows you to more quickly inspect, validate, debug data collection and experiences for your mobile app (Figure 5).
Project Griffon is in active development and is adding new features and enhancements at a rapid pace to not only help customers troubleshoot and validate experiences with Adobe solutions but to expand validation capabilities for ourAdobe Exchangepartners. Read more about Project Griffonhere.
Solid documentation and great support
We’ve taken a lot of time to developdocumentationto guide you through the use of these new tools. We continue to add information for our users including code snippets organized by platform, sample tutorials, and implementation articles. We have also developed documentation on best practices formigrating your mobile implementation from our v4 SDKs. If you are looking for an answer to a question and cannot find it in our documentation, make sure to shoot us a question in ourcommunity forums. Adobe Consulting Services are also available to help with all implementation needs.