Adobe Experience Manager Mobile 2016.14 Release
The Experience Manager Mobile team released version 2016.14 on Tuesday, December 6.
Initial Support for App Customization
The ability to change colors and fonts in the app UI is the first of several upcoming app customization features. Customizing apps offers more control over the user experience and helps ensure consistent branding. In the On-Demand Services Portal, you can specify different colors and fonts for various views that appear in your app, including the app navigation bar, the app menu, and sign-in and paywall screens.
Android Push Notifications via On-Demand Services Portal
Push messages appear outside of your app, making them useful for re-engaging passive users or conveying time-sensitive information. Android push notifications are now available through On-Demand Services. You can send Android text notifications using the Notifications section of the On-Demand Services Portal or by using APIs. (As a separate feature, you can also send push notifications using the Mobile Marketing Dashboard.)
New App-Signing Process
Adobe has changed its app-signing process in order to comply with Apple guidelines and use the most current version of Xcode. The Apps section of the AEM On-Demand Portal includes a new update for the AEM Mobile Signing Tool. Once you update the AEM Mobile Signing Tool, you select the certificate from your computer’s keychain instead of specifying the .p12 certificate and password. To use this new signing method, Xcode 8 and Java 7 or later must be installed on the computer, and the certificate must be available in the computer keychain. (You can double-click a .p12 certificate and specify a password to add it to the Keychain Access tool.)
Support for iOS ATS Compliance
Starting January 1, 2017, Apple will require all apps to connect securely to servers. AEM Mobile apps that connect to content through hyperlinks, entitlement calls, or other URL links should use HTTPS domains. If you need to use HTTP instead of HTTPS domains, make sure that you select the new “Allow content from HTTP” option when building your iOS app to ensure that HTTP content loads in your app. If this option is not selected, HTTP content will not load in your app. After January 1, 2017, you might need to justify your use of HTTP to Apple during the submission process.
Custom Authentication Support for Gigya
Custom authentication offers greater control over the authentication process and can customize the sign-in experience in AEM Mobile apps. Custom authentication now supports Gigya, which allows customers to sign in using both traditional and social media methods such as Facebook and Google.
Bugs Fixes and Enhancements
All app platforms now include an auto-generated “Acknowledgements” page. If you open the app settings and choose Acknowledgements, a list of licenses is displayed. This release includes additional bug fixes and enhancements.
–Experience Manager Mobile Team