The We.Travel sample app is pre-implemented with the Adobe Mobile Services SDK v4. You just need to update it, so that it points to your own Experience Cloud Org and solution accounts.
At the end of this lesson, you will be able to:
Download the sample-app-android-SDKv4-Base-Version.zip
Decompress the zip file
Open the app in Android Studio as an existing project (ignore any errors about “Invalid VCS root mapping”)
Run the app in an emulator to confirm that the app builds and you can see the home screen
Browse the app and verify that you can complete the booking process (select any payment optin and just hit “Proceed” to skip over the billing screen!)
The Adobe Mobile Services SDK has been preinstalled within the We.Travel app according to the documentation. Now you will update the installation to point to your own Target account.
First, create a new App in the Mobile Services user interface:
Log in to the Adobe Mobile Services interface.
Go to the Manage Apps, then click Add to add a new app to use with this tutorial (Manage Apps > Add).
Choose an an Analytics report suite with non-production data, give the app a name, select the Standard type and click Save.
Once the app has been added, add your Target Client Code on the next screen in the SDK Target Options section (you can find your client code in the Target interface under Setup > Implementation > Edit Settings, next to the Download
The Request Timeout setting determines how long the app waits for the response from the Target server before executing timeout instructions. Just leave the default setting.
Enable the Visitor ID Service and make sure your Organization is selected in the drop-down.
Save your changes by clicking Save on the top right side of the window (not the one in the Universal Links, App Links options, or Push Services section).
Scroll to the App SDK Downloads section at the bottom of the page and download the Config File:
ADBMobileConfig.json file in your Android Studio project assets folder (app > src > main > assets).
Now open the
ADBMobileConfig.json file and make sure it contains the expected changes such as your Target Client Code and your Analytics details:
If you don’t see your settings, confirm that you clicked the right Save button in the Mobile Services interface and copied the file to the correct location.
Congratulations! You’ve updated the SDK with your Target account details! We will do additional validation of the configuration after we add Target requests in the next lesson.