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.
Web-based DPS App Builder now supports building Windows apps. See Building DPS apps for Windows.
The v32.3 release includes bug fixes for iOS viewers. For details, see DPS Bug Fix Release Notes.
Note the following:
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.
Legacy Content Viewer for Android to be 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.
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.
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.