Swiftpack.co - Package - dangermouse007/v5-aep-sdk-partner-demo

Partner Mobile Accelerator - v5mobile - AEP SDK

This project is based on the the newly released Adobe Experience Platform SDK for Mobile and has been adapted to be easily integrated in the partner sandbox environment.

Disclaimer

This project is solely to be seen as a demo app of the v5 capabilities and accelerator and not a production ready implementation.

SDK V5

In this demo app you will be using the Adobe Experience Platform SDK for iOS or Android. The SDK will support more platforms to come like React Native.

Download SDK

The app does already include the latest version through CocoaPods or Gradle but if you want to update the SDK feel free to do so. Be aware that updates might effect the code base. Please test it thoroughly.

Important Links

Note that by default you should always use the library dependecies that your Launch environment configuration suggests you when clickig on Install under Environments.

  1. Gradle
implementation 'com.adobe.marketing.mobile:analytics:1.+'
implementation 'com.adobe.marketing.mobile:target:1.+'
implementation 'com.adobe.marketing.mobile:userprofile:1.+'
implementation 'com.adobe.marketing.mobile:sdk-core:1.+'
  1. iOS
pod 'ACPAnalytics', '~> 1.0'
pod 'ACPTarget', '~> 1.0'
pod 'ACPUserProfile', '~> 1.0'
pod 'ACPCore', '~> 1.0'

Requirements for Push and In-App messages

If you are part of the beta please look at these requirements:

  1. ACS 18.9 or higher
  2. Adobe Launch Integration
  3. Adobe.IO Integration setup for Launch
  4. TechOps connect ACS instance to Launch with Adobe.io details
  5. TechOps provision MCIAS endpoint (Experience Platform In App Service)
  6. AEP SDK Campaign Beta 1.0.2 only for iOS available. Android in development

The Podfile references the following libraries:

# Pods for v5mobile
pod 'ACPAudienceBeta', '~> 1.0.2beta'
pod 'ACPCampaignBeta', '~> 1.0.2beta'
pod 'ACPAnalyticsBeta', '~> 1.0.2beta'
pod 'ACPTargetBeta', '~> 1.0.2beta'
pod 'ACPUserProfileBeta', '~> 1.0.1beta'
pod 'ACPCoreBeta', '~> 1.0.2beta'

Installation

Have a look at the indiviual iOS README or Android README for more steps.

Setup Analytics

Create a new Reportsuite based on the Mobile Template and within the Reportsuite settings > Mobile Application Reporting enable App Reports and Location Tracking.

In addition you can also configure processing rules for the context data.

Configure Launch

Create a new mobile property. Go to Extensions > Catalog and install Mobile Core, Profile, Analytics, Target, Campaign. Configure every extension and build your library. Under Environments click on the install button to get your config id.

Once the Launch API is publicly available I will update the below Postman Collection to let you auto-create the complete mobile property

In-App Messages Configuration

In Launch you need to configure Data Elements and Rules besides the Campaign extension.

  1. Data Elements
  • camp-server - Data Element Type - Free Form > Value: ~state.com.adobe.module.configuration/campaign.server
  • pkey - Data Element Type - Free Form > Value: ~state.com.adobe.module.configuration/campaign.pkey
  • mcid - Data Element Type - Experience Cloud ID
  1. Rules
  • IAM-Tracking - Action > Send Postback > Value: https://{%%camp-server%%}/r/?id={%%id%%}&mcid={%%mcid%%}

  • Detailed setup guide

Push Configuration

How to configure the mobile app channel in Adobe Campaign Standard and AEP SDK.

A major change from SDK 4 to 5 is that there are rules to collect PII in Launch now instead of coding some of the logic into the app.

AEM CaaS

Requirements

The AEM package was built on AEM 6.4.0 with sample content. It has no major dependencies in the code but if you run it with -nosamplecontent please make sure to look at some component dependencies. I used:

  • core wcm components all 2.0.4
  • core wcm components extension 1.0.0
  • we-retail-all (3.0.0)

Configure

  1. Install the AEM CaaS package on Author and replicate to Publish
  2. Point the app to your AEM Publish instance and path to the API Data Endpoint (the app has already defaults to your local AEM instance)
  3. Add a new Asset based on the Location Content Fragment Model and embed it into the existing API site under Sites > We.Retail > Api > Locations

Alternative to AEM

If you want to demo the JSON feed into the app without AEM, just host the locations.model.json on your own webserver instance and change the app config accordingly

Existing links to mobile app demos:

Resources

Built With

Contributing

Please give me feedback on any section of this app - code, documentation, bugs, ...

Versioning

Current version is 1.0

Roadmap

  • Add app to app store
  • Reflect full api coverage in the app

Authors

Acknowledgments

  • Looking forward to your contributions

Github

link
Stars: 1
Help us keep the lights on

Dependencies

Used By

Total:

Releases

1.0 - Nov 17, 2018

This is the initial release after the office hours session. It contains the iOS app and a very basic Android version.