The following features are scheduled to be available for the v32 release.
For a compilation of release notes, see History of new feature release notes.
For a list of bug fixes, see DPS Bug Fix Release Notes.
This release includes minor bug fixes for iOS and Android viewers. For details, see Bug Fix Release Notes.
Article name now included in article metadata (iOS)
The FolioDataService previously included Title, Description, Byline, and Kicker properties in the Reading API. With this release, the Name field is now available for iOS viewers. This allows publishers to obtain the Article Name and build navto: links dynamically.
AuthenticationService now supported (iOS)
The Reading API now includes AuthenticationService, which was previously available only in the Library/Store API but not in the Reading API. The AuthenticationService API is used for direct entitlement authentication in iOS viewers. However, this API does not include all the same capabilities included in the Library/Store API. You can check whether the user is logged in and retrieve the username and auth tokens, but you cannot log in, log out, or display the native sign-in dialog box.
For details, see Reading SDK.
Several bugs were fixed for iOS viewers, including the black bar display problem that occured in apps in which the "Enable auto-hiding of vertical scrollbar" option was selected. For details, see Bug Fix Release Notes.
DPS App Builder now requires new app icon and launch images to support Apple guidelines. Required app icons include 87x87 and 180x180 sizes for the iPhone 6 and 6 Plus devices. The 120x120 icon was previously optional and is now required. New launch images include 750x1334 and 1242x2208 sizes. The 1136x640 launch image is now required.
All apps are now required to supply a 1024x1024 image for the App Store. DPS App Builder previously asked for optional 1024x1024 and 512x512 artwork images.
DPS App Builder has new requirements for Newsstand icons, which now must have 512 (SD) or 1024 (HD) pixels on the longest edge. Previously, DPS App Builder required a 96x128 image for SD devices and a 192x256 for HD devices. DPS App Builder now requires 384x512/512x384 or 768x1024/1024x768 images for Newsstand.
The DPS Asset Generator supports these new sizes. See Working with the DPS Asset Generator.
Additional rendition sizes are now supported for targeting iPhone 6 (1334x750) and 6 Plus (1920x1080 physical; 2208x1242 logical) devices.
Although these additional folio sizes are now supported for renditions, we recommend that you create 1136x640 folios for iPhone 5 and higher.
A bug was fixed for iOS viewers in which Apple was rejecting some apps because the bundle string was longer than 18 characters. The bundle string for iOS viewers now begins with v32.5. For details, see Bug Fix Release Notes.
In case you missed it, Fast Company worked closely with Adobe to launch a new mobile app that provides a preview of a completely re-imagined mobile experience that Adobe will bring to market in the summer of 2015. For details, see New Fast Company App Reveals Adobe’s Vision for Future of Digital Publishing.
An iOS viewer team fixed a bug in which the Buy button appeared for entitled folios in some instances. For details, see Bug Fix Release Notes.
DPS App Builder no longer includes an option to create or update v31 apps because v31 apps do not include 64-bit support. With the updated DPS App Builder, you can create v32 apps with 64-bit support that comply with Apple requirements. For details about 64-bit support, see the next section below.
With the server-side update to DPS App Builder, you can build v32 apps that are compliant with the most recent Apple App Store requirements to include 64-bit versions of apps.
There is no need to rebuild existing apps. Starting February 1, Apple requires only new app submissions to have 64-bit support. Any v32 app created after January 12, 2015 will have 64-bit support. You can update your apps whenever it is convenient for you.
Adobe will not introduce a 64-bit compatible version for v31 apps. As a result, the ability to build v31 apps will be removed from DPS App Builder in the release scheduled for February 2, 2015. You can upgrade your v31 apps to v32 (with 64-bit support) at your leisure.
When a push notification for a new folio is sent, that folio is downloaded in the background of any non-Newsstand app as long as users have enabled push notifications and are using a device running iOS 8 or later. This feature is supported for v32.1 and later apps.
For details, see the Push notifications help article and Triggering Background Downloads via Push for iOS8 Viewers.
DPS apps can now take advantage of the full screen space on supported Android devices. For Android devices that support soft keys instead of hardware keys for back, home, and menu navigation, v32.4 and later Android apps use the full screen to display content.
The Adobe Content Viewer offline extension for Chrome allows readers to view DPS web viewer content offline. If you want your customers to be able to read your web viewer content offline, make this link available to them, and ask them to open this URL in the Chrome browser and follow the instructions:
For more information, see Offline web viewer browsing in Chrome.
The Store Configurator is a web-based service that assists you in building custom libraries and stores for DPS apps. The Store Configurator now includes options for creating welcome screens and slideshow library banners. For an article about creating library banners, see Creating Slideshow Library Banners Using the Store Configurator in the DPS Developer Center. Note that the Store Configurator is a companion service; Gold support does not provide troubleshooting assistance.
The v32.4 release includes bug fixes for iOS viewers. For details, see DPS Bug Fix Release Notes.
iOS 64-bit Support
Beginning February 1, 2015, Apple will require all new apps submitted to the App Store to include 64-bit support and to be built with the iOS 8 SDK. The DPS release scheduled for January 2015 will include an update to the v32 iOS viewer version that complies with this Apple requirement.
If you have an existing app in the App Store, you are NOT required to rebuild your app.
Note the following:
Legacy Content Viewer for Android is now retired
To deliver a more engaging reading experience on Android tablet and phones, we encourage customers to use the native Content Viewer for Android. The native Android viewer offers extended capabilities as compared to the legacy, AIR-based Content Viewer for Android. Note that with the December 2014 release of DPS, the legacy, AIR-based Android viewer will be retired and no longer supported. Please review the Native Content Viewer for Android FAQ for more information.
For information about the native Android viewer, see Building native DPS apps for Android.
DPS Single Edition to be retired
The Digital Publishing Suite, Single Edition, service will be available for use until May 1, 2015. Customers can redeem previously purchased serial numbers and create or edit apps in the meantime. However, after May 1, 2015, using DPS Single Edition to build or edit apps will no longer be available. On December 4, 2014, Single Edition will no longer be available as a purchasable product from the Adobe.com store.
InDesign CS5.5/CS5 and DPS support in v32
With the v32 release, DPS no longer supports InDesign CS5/CS5.5. InDesign CS5/CS5.5 users can no longer create folios or articles or upload content to the Folio Producer Service. For details, see DPS and InDesign CS5 and CS5.5 Support.
DPS App Builder requirements
Note the following:
Restriction to the number of folios in Folio Producer
With v32, publishers are limited to publishing only 1,000 folios in the same Folio Producer account and 1,200 articles in a folio. If you need to publish more than 1,000 folios in an app, you can use a workaround described in DPS high-volume workflow.
Web-based DPS App Builder now supports building Windows apps. See Building DPS apps for Windows.
The v32.2 release includes several important bug fixes for iOS and Android viewers. For details, see DPS Bug Fix Release Notes.
The v32.2 version of the Adobe Content Viewer (iOS only) now includes an option to sign in using an Adobe Experience Manager (AEM) account. The v32.2 version of the Adobe Content Viewer has not yet been approved by Apple, but you can use DPS App Builder to create a custom version of the Adobe Content Viewer until the updated version becomes available.
When you select the AEM tab in the Sign In dialog box and sign in using an AEM account, you can preview folios without having to publish them to the Folio Producer Service.
Cover images in the Adobe Content Viewer library include new badges to indicate the origin of the folio.
For more information about using AEM and other Content Management Systems with DPS, see Efficient DPS workflows leveraging CMS systems.
DPS Export for PowerPoint is a PowerPoint add-in that converts Microsoft PowerPoint 2010 and 2013 presentations to Adobe DPS folios. When you install DPS Export for PowerPoint on a Windows computer, a "DPS Export" add-in tab appears in PowerPoint. You can then specify export settings and create a folio from the slide deck. Each slide in the presentation becomes a separate PNG article. Animations can be converted into image sequence overlays, and hyperlinks are preserved.
For details, see DPS Export for PowerPoint.
Local notifications are now supported in v32 apps on iOS 8 devices. When you send a background push notification, you can send a message to users who have accepted push notifications but are not entitled to the folio. Users can then view the message or click a reminder button to receive the message later.
In addition, background downloading in non-Newsstand apps on iOS 8 devices is now supported.
See Push notifications for details.
The CRM integration APIs are now supported on Windows viewers. See Integrating DPS with CRM systems such as Salesforce.com.
If you create a button using the navto://relative/reset format, users can tap the button to jump back to the first article and clear article reading positions. This option is especially useful for kiosk and demo apps. This format is supported in iOS, Android, and Windows viewers, but not in web viewer.
CRM Integration APIs
Publishers can store their customer information in encrypted format on the iOS device. The Library & Store APIs now include the EncryptedStorageService API that encrypts and stores objects in an SQL Ciper database in the local app storage. This option is iOS only. For more information, see Integrating DPS with CRM systems such as Salesforce.com in the DPS Developer Center.
Push notification APIs now available
Enterprise publishers can customize their workflows using push notification APIs. These APIs are currently iOS only. API documentation will be available soon in the DPS Developer Center.
New optional Article Preview experience
The DPS team created an alternate Article Preview experience designed to make a clearer distinction between free and protected folios and to provide readers with easy access to the next free article. To enable the alternate article preview experience, Enterprise publishers need to add custom config code to their custom entitlement banner .zip file.
This alternate preview experience works only on iPads with iOS 7 or later. Metered articles are treated as protected. In addition, the app requires a custom entitlement banner. For more information about enabling the alternate Article Viewer experience, see Configuring the Alternate Free Article Preview Experience.
Additional iOS viewer changes
For information about building native Android apps, see Building native DPS apps for Android.
For more information about building Windows apps, see Building DPS apps for Windows Store.
For a feature comparison chart, see DPS supported features list.
Push notification certificates are now managed in the Push Notifications Service on the DPS Dashboard, making it easier to update push certificates and be alerted when your certificates are expiring.
Use DPS App Builder to indicate that your app is enabled for push notifications and whether you're using the Adobe push service or a third-party push service. Use the Push Notifications Service to specify your push certificates and passwords. Push certificates are stored on a server, not in the app itself.
Note the following:
For information about push notifications, see Push notifications.
To see a list of other DPS features included in v31 dot releases, see History of new feature release notes.