Target for mobile apps FAQ
List of frequently asked questions about Target for mobile apps.
Does the Mobile SDK integration allow for roll-out of new mobile functionality? Can I turn the feature flag on and off without new code deployments?
Yes, you can use our mobile SDK to roll out features gradually.
For more complex logic, should I develop directly in the app instead of using the Mobile VEC? If so, which development language should I use?
Currently, the VEC supports common use cases such as changing the image, text, color, etc. For more advanced use cases, such as personalizing the app layout, you must insert the Target request/location (mbox) in the code and use the Form-Based Experience Composer to design the experiences and allocate traffic. Our mobile SDK supports Java, Objective C, and Swift. It depends on your team's preference and resources to choose the language.
Which SDKs are available today?
The Adobe Experience Platform Mobile SDKs currently support iOS, Android, and React. For more information, see the Adobe Experience Cloud Platform Mobile SDKs guide .
What is the frequency of the location-based feature, in terms of verification about the latitude and longitude?
See the Adobe Places documentation for more information.
Which native classes do mobile "Views" support? Do they support any NSObject derived class (or any Android Object) or just NSViewController and Activities?
For more information, visit the Android documentation for the manual way of declaring views .
Do I need at.js for the Adobe Experience Platform Mobile SDKs to work?
Is there a mobile app integration between Adobe Experience Manager (AEM) and Target mobile activities?
It is on our roadmap but there is no timeline yet. Currently, you can share JSON Experience Fragments from AEM to Target and there might be potential to then use them in a mobile app activity.
Can I add more images using the VEC or only change existing images?
You can currently change existing images only.