Reminder - Digital Publishing Suite (DPS) will End of Life on August 31st, 2019.
by Amit Gupta
Table of contents
24 September 2013
Note: If you have questions about this article, use the tutorial feedback link at the bottom of the article. Please don’t contact technical support with questions about Adobe Developer Connection articles.
With iOS 7, Apple is introducing a new dynamic user interface (UI) with the use of depth and translucency, making the UI radically different than any current mobile operating system such as iOS 6 and Andriod.
Per Apple, there are three main UI themes assoiated with iOS 7:
- Deference. The UI helps users understand and interact with the content, but never competes with it.
- Clarity. Text is legible at every size, icons are precise and lucid, adornments are subtle and appropriate, and a sharpened focus on functionality motivates the design.
- Depth. Visual layers and realistic motion heighten users’ delight and understanding.
Adobe DPS Viewer is supporting the new iOS 7 UI with its R28 release. As part of this, the DPS Viewer will switch to standard UI elements provided by iOS 7; note that almost all UI elements in DPS apps were custom elements built by Adobe. This switch to native operating system UI elements enables the adoption of the above mentioned themes of iOS 7. Use of standard elements also ensures that the UI automatically receive updates if Apples introduces a redesigned appearance in the future.
Switching to native/standard UI elements provided by iOS 7 leads to functionality changes in DPS apps. Below is a list of changes in R28.
Bottom navigation bar (see screenshot 1 and 3 in appendix) that has custom web slots and icons for ‘Library’ and ‘Viewer’ will increase to 56 pixels (from 44 pixels in R27) on the standard resolution iPad. On the iPhone, the navigation bar height will increase to 49 pixels (from 44 pixels in R27).
Additionally, the navigation bar will now support an icon (which is uploaded using DPS App Builder) and a label for the icon. The label will be entered by the Publisher using the DPS App Builder tool and can be localized to various languages. The icon size would be 30x30 pixels for the standard definition iPad and iPhone, and 60x60 pixels for the retina display. The icons should be in one color with alpha (see screenshot 2 in appendix). Apple requires that these icons be in PNG format.
Note that icons, in general, in iOS 7 are thinner and lighter, and a publisher may want to change existing icons to match the new iOS 7 style.
The horizontal spacing between the slots/icons in the bottom navigation bar is controlled by the operating system, and changes based on the number of icons configured in the bar. In general, the spacing in R28 is greater than the previous in prior releases. This change is more evident on the iPhone than iPad.
Note that the label text is not truncated by the operating system, so labels of adjacent slots can overlap if they are too long. Our recommendation is to use a string with a maximum of 10-13 characters. The best way to test that your labels don’t overlap is to check your navigation bar in a development app.
Furthermore, instead of providing three icons for each web slot (that represent the Up/Down/Disabled states), publishers would be required to provide a single monochromatic icon, and the operating system will automatically display the states.
Note that an inactive slot color code is #919191. Active slots color code is #00aadd.
Also, the icon and label are only visible when the navigation bar slot is available. No disabled state is required because the operating system will hide any when it cannot be used. For example, when no folio has been loaded in folio view, the ‘Viewer’ icon will not be displayed in the navigation bar.
The folio view navigation bar appears when a reader taps on content. With R28, apps will display the 20-pixel Apple status bar (that shows the time, battery life, etc.) above the folio view navigation bar. This change is reflected on both the iPad and iPhone, and is applicable for both iOS 7 and iOS 6.
Note that as result of bottom navigation bar increase in height and display of status bar, an additional 32 pixels of content would be obscured on display of the folio view navigation bar on iPad.
iOS 7 requires a change in the app icon size. Below are the new additional app icons sizes required for building both R28 and R27 apps in App Builder.
- Size for all iPhones: 120 x 120 pixels.
- Size for high resolution iPad: 152 x 152 pixels.
- Size for iPad 2 and iPad mini: 76 x 76 pixels.
Note that Apple requires these icons to be in PNG format.
Additionally, please refer to Apple Developer’s site for any additional icons that may be required for app submission. Here is the relevant link: https://developer.apple.com/library/prerelease/ios/documentation/UserExperience/Conceptual/MobileHIG/IconMatrix.html#//apple_ref/doc/uid/TP40006556-CH27-SW1
With V28, your app will use the new native sharing experience on iOS 7 and keep the existing sharing menu on iOS 6. The new sharing interface (Activity Sheet) supports sharing options that have been available previously but in a new format. The Activity Sheet also offers sharing via AirDrop (see screenshot 4 in appendix) on devices which support this feature.
With V28, the overall UI will have a lighter color theme on iOS 7, while on iOS 6 the background color will continue to be the existing darker shade. In case you’re using a custom web slot, please adjust the background color of your custom web slot appropriately.
With R28, publishers will have the option to lock the orientation (landscape or portrait) of the Viewer using a setting in App Builder. Note that this setting will lock the library, any custom web slots, and the folio view. This new setting in App Builder will override the custom web slot orientation setting.
With V28, Adobe DPS is dropping support for iOS 5, which is the highest iOS version supported on iPad1. Thus, V28 apps will not run on iOS 5, and by extension, on iPad1. As a result,
- Current subscribers on iPad1 will be able to download future content on their existing apps only if publishers continue to create folios with a target viewer version that matches their pre-V28 viewer version that is on iPad1.
- New/existing Readers using iPad1 will not be able to install/upgrade to V28 (or later) apps. However, these iPad1 readers will be able to download the last compatible version, that would be V27 or lower, if it already exists in the App Store.
If business reasons require a new publisher to be on iOS 5, an option to create a V27 app using R28 App Builder would be available for Enterprise and Professional publishers. This app will be certified on iOS 7, but would not take advantage of the new UI themes that Apple is introducing with iOS 7.
iOS 5 End of Life Questions and Answers
What happens to existing readers on iPad1 who have subscriptions that entitle them to future content?
Readers with pre-V28 apps on iPad1 will continue to receive your published folios provided you continue to create your folios with a target viewer version that matches your pre-V28 app. For example, let’s say that your pre-V28 viewer version is V26. After R28 is released, you build and distribute a V28 app. Your legacy iOS 5 and iPad1 readers will continue to use V26. To ensure that your subscribers on iPad1 continue to receive the new folios, you should continue to author your folios with a viewer version target of V26. These folios will download on both the V26 app on iPad1 and V28 app that is available on newer Apple devices.
What happens to my existing Readers when they attempt to upgrade to a V28 app on from iPad1?
When Readers attempt to download the app over the air, they will receive the following message, “The current version requires iOS 6.0 or later, but you can download the last compatible version.” See screenshot 5 in Appendix. This would allow readers to upgrade to the latest version of the app that is compatible with iOS 5, but not V28. When readers launch the App Store and navigate to the ‘Upgrades’ tab, the V28 app will not be available.
Readers will not be able to upgrade to V28-based Viewer by manually syncing the apps on iPad1 with their iTunes Library.
What do iOS 5 and iPad1 readers that haven’t downloaded my app see?
There are two scenarios to consider.
- Older version of the app that is compatible with iOS 5 is available in the App Store. When Readers attempt to download the app over the air, they will receive the followinga message, “The current version requires iOS 6.0 or later, but you can download the last compatible version.” See screenshot 5 in Appendix.
- Older version of the app that is compatible with iOS 5 is not available in the App Store. When Readers attempt to download the app over the air, they will receive the following message, “Update Required. This app requires iOS 6.” Readers will not be able to download V28 on iPad1.
In both scenarios above, iPad 1 Readers will not be able to upgrade to V28-based Viewer by manually syncing the apps on iPad1 with their iTunes Library.
What happens if an existing reader deletes their existing app from iPad1?
iPad1 readers will be able to install the latest compatible version of the app, which would be V27 or lower, from the App Store. Readers will not be able to download V28 or later from the App Store.
R28 DPS App Builder will create V28 and V27 apps. Will the V28 app not work on iPad1?
With R28 DPS App Builder, Enterprise and Professional customers can create a V27 app that would continue to work on iOS 5, and thus, on iPad1. Adobe DPS will certify this V27 app on iOS 7 as well. However, this app will neither take advantage of the significant UI upgrades that Apple has made in iOS 7 nor the AirDrop feature. Single Edition customers will not be able to create a V27 app.
I’m currently on a V25 or V26. What is Adobe’s recommendation with R28?
Adobe recommends to evaluate V27 features. If you care about V27 features for iPad1 readers, upgrade to V27 first, and then upgrade to V28. This will ensure iPad1 Readers download V27, and iOS 6 or 7 readers download the V28-based app.
In case you don’t care about the V27 features for iPad1 readers, then you should upgrade to V28.
I currently don’t have a DPS-based app in the App Store. What is Adobe’s recommendation with R28?
If you are an Enterprise or Professional customer and care about acquiring readers on iOS 5/iPad1, you should build a V27-based app first, and then upgrade to a V28-based app. This will ensure iOS 5/iPad1 readers download V27-based app, and iOS 6 or 7 readers download V28-based app.
If you don’t care about acquiring readers on iPad1, you should build a V28-based app.
Adobe DPS recommends updating to a V28 app that supports the new UI changes that Apple is introducing.
With the iOS 7 release, Adobe DPS is stopping support for iOS 5 in V28. If business reasons require Publishers to support iOS 5, they should create a V27 app using R28 App Builder first, and then upgrade to V28. This app will be certified on iOS 7, but would not take advantage of the new UI themes being introduced with iOS 7.
Thus, with R28
- The V28 app will run on iOS 7 and iOS 6. The UI has been optimized for iOS 7. The V28 app running on iOS 7 will have a light UI. The same app on iOS 6 will have the existing dark UI. On both iOS 6 and iOS 7, changes related to top and bottom navigation bars, status bar, app icons are applicable.
- The V27 app will run on iOS 7, iOS 6, and iOS 5. This app will have the older dark interface, and will not have any of the changes stated in this document.
Screenshot 1: V28 Library on iOS 7 with bottom navigation bar
Screenshot 2: Bottom navigation bar icon example that has one color with alpha
Screenshot 3: V28 Folio View on iOS 7 with bottom navigation bar
Screenshot 4: V28 sharing menu (Activity Sheet) on iOS 7
Screenshot 5: Reader experience on iOS 5 or iPad1
- Updated to clarify that DPS Single Edition users cannot specify an older viewer version
- Update the document to reflect Apple's new support for the ability to download the last compatible version of an app for your device.
Comments are currently closed as we migrate to a new commenting system. In the interim, please provide any feedback using our feedback form. Thank you for your patience.