In previous versions of the Mobile SDKs, you would use Adobe Mobile Services (http://mobilemarketing.adobe.com) to set your SDK configuration parameters. After making all of your config setting changes you would then download a JSON config file to use in conjunction with the SDK package that you would download from our public git.
In Adobe Launch you now have the capability to create a mobile property. We've separated the Core SDK out as an extension, along with additional extensions for other Adobe Experience Cloud solutions. You can add the appropriate extensions to your SDK build as appropriate and then create a new build for Development/Staging or Production. By creating multiple environments, you end up creating different configuration endpoints that can be dynamically updated depending on which application they are connected to. i.e. Development environments can be wired into a developers XCode or Android Studio project, while the staging environment can be linked to a version of the app that is in TestFlight. Once you have completed your development and are ready to release your app, you will want to make sure that you have linked the SDK configuration up to Launch's production environment endpoint.
For each environment that you create, Launch will generate a set of installation/initialization instructions that work with familiar dependency managers such as Maven and CocoaPods. When you use one of these dependency managers in conjunction with your application build, you no longer have to go and pull down a version of the SDK or any extensions. The dependency manager will go out to each linked source repository and make sure that you are getting the latest approved version for deployment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.