Adobe DPS 26: PDF article support in Android and Desktop Viewer

The following features are available for the v26 release:

Free Article Preview (iPad only): you can allow customers to preview content in a retail folio. Users can tap the Preview button to download and read all free articles. When a user navigates to other articles in the app, a paywall prompts them to purchase the folio. To enable Free Article Preview in a retail folio, select the “Enable Article Preview” setting in the Account Administration Tool, and use the Folio Producer Editor to mark specific articles as Free. (Free Article Preview is iPad-only and currently does not work with folios that have Sections.)

 PDF article support in both Android Viewer and Desktop Viewer: PDF articles are now supported on Android devices and in the Desktop Viewer. On Android viewers, you can take advantage of the PDF format to reduce file size, reuse iOS folios that have PDF articles, and use pinch & zoom on article pages. In the Desktop Viewer, you can now preview folios that have PDF articles, which is especially useful to preflight your folio for errors. The app version needs to be v26 or later to display PDF articles, but the folio with PDF articles can be any version. For a video demo, see the PDF Content on Android video. (Note that this is a change to the existing AIR-based Android viewer, not to the native Android viewer that is currently in development. In addition, PDF support on Android does not include displaying PDF files in the in-app browser.)

iPad library improvements: Icons now appear beneath each cover preview image in the library so that users can see which content is free or retail without an extra tap. Tapping a button with a price initiates a purchase. Tapping the free button or the cloud button initiates a download. A cloud icon appears if a user is entitled to a retail folio that hasn’t been downloaded. Tapping the cover preview image itself still displays a preview pane with additional information. If a custom library is configured to display only entitled folios, the preview pane does not appear when tapping the cover image. (Enterprise only) If your custom library displays only folios to which your customers are entitled, no preview pane appears. Tapping a cover image begins to download the folio.

Full iPhone 5 support: You can now create 1136×640 folio renditions to avoid letterboxing content on the iPhone 5. In DPS App Builder, you must specify an additional 640×1136 launch image (splash screen) to comply with Apple requirements for iPhone 5 apps.

DPS App Builder includes the following changes:

  • Asset links are now stored on the server, allowing you to use different computers to build the app without having to relink to copied assets. For example, an agency can go through DPS App Builder to specify most of the settings and files, and the client can then complete the app by specifying the certificates. When you edit an existing viewer, an “Asset stored on the server” message appears in the text field. Storing assets works only for an individual app; you cannot store assets on the server for use across multiple apps.
  • (Enterprise) When you create a custom store that takes advantage of new API features, creating a custom library is no longer required.
  • (Enterprise) If you want to continue using an older store that you’ve created, you can select Use Legacy Store APIs in DPS App Builder. However, if you select this option, you cannot specify a custom library.
  • The “Enable hot zone to display folio view controls” option now includes a hot zone at both the top and bottom of screen, not just the bottom.
  • There is a new option for specifying an optional privacy policy URL that appears in the library settings menu.

Web Viewer now includes the following improvements:

  • Embedded Web Viewer. You can now embed shared Web Viewer articles in your Web site with new support for iframe HTML tags in DPS. Include surrounding design elements that convey a consistent, branded experience for your customers. For a video demo, see the Embed Publications within Web Sites video. For an article with detailed instructions, see Embedded Web Viewer.
  • Web Viewer-only folio. You can create a special folio rendition for the Web Viewer that appears only in the Web Viewer browser, not on the device viewer. For example, you can create a 1024×580 folio that displays only a horizontal orientation, uses terminology such as “click” instead of “tap,” and replaces an unsupported panorama with a static image. See Creating a Web Viewer rendition.
  • Custom stores and custom Libraries are now supported in Web Viewer. Integrate a Custom Store and Custom Library within the Web Viewer to feature special content, offers, or promotions. Check the DPS Developer Center for information.
  • Optional privacy policy URL. You can configure a web link to your app’s privacy policy. This is supported in both iOS and Android Viewers.
  • Web Viewer analytics. Analytics data is now enabled for the Web Viewer.
  • Horizontal Swipe Only support (added in v25). The Web Viewer now displays “flattened” articles that have Horizontal Swipe Only selected.

New and enhanced Fulfillment Reports: The Fulfillment Report on the DPS Dashboard gives publishers easy-to-understand details related to the downloads of their folio content. The Fulfillment Report now includes additional data fields to make it easier to build informative pivot tables that show how many downloads for each publication, per issue, with a total for all downloads and a breakout showing web viewer downloads separately. A new Consolidated Fulfillment Report (currently called “Rollup Report”) gives administrators the fulfillment data for all publications associated with their account. Finally, all report data is now recorded daily instead of weekly.

Online purchase of fulfillment bundles:  A new online purchase option for 10,000 Fulfillment Bundles makes it easy for publishers to ensure their account is always in good standing. Fulfillment renewals placed through a reseller or directly from Adobe can sometimes take a few days to process. To provide a faster purchase option, publishers can now buy a serial number for a 10,000 fulfillment bundle through the Adobe Store and redeem that serial number through the DPS Dashboard.

Analytics improvements:
  • Complete articles read. You can track how many readers completely read articles in a single visit.
  • TOC tracking. You can track taps on the TOC button and also identify which articles are discovered through the TOC.
  • Readers that are directly entitled by publishers. You can get data about readers who sign in to the app and obtain folios through direct entitlement. You can optionally return the reader’s subscriber ID and subscriber type through the direct entitlement API. The subscriber type and subscriber ID values are passed to SiteCatalyst so that you can track how these subscribers engage with the folio.
  • Free Article Preview. When customers tap the “Preview” button to preview the issue, the number of preview button taps and the free articles that get previewed are tracked. The number of conversions after the issue is previewed is also tracked.
  • Omniture Visitor ID and Push notification token. For each reader, an Omniture visitor ID and push notification token (if the reader has opted in to receiving push notifications) is added to SiteCatalyst.
  • Web Viewer: Web Viewer information is tracked.

First Folio Free API improvement: Enterprise publishers can now use the custom library API to configure the subscription banner to display messaging depending on whether the reader is a subscriber and can appropriately provide messaging that supports the latest free retail issue feature.

Advertisements

As Android tablets grow, publishers struggle to match the iPad experience

When the IDC forecast past month that Google’s Android operating system would soon surpass Apple’s iOS in tablet market share, publishers of digital magazines could be excused for some handwringing.

Since 2010, Apple’s dominance of the market allowed publishers to reach the majority of the tablet audience by targeting just one device: the iPad. But times have changed.

Thirty-one percent of American adults now own tablets, according to Pew. Much of the growth in the market is being driven by device proliferation, and many of these devices run Android.

The Nexus 10 Android tablet
A Google employee browses magazine issues on The Nexus 10 tablet at a Google announcement in San Francisco last fall. (AP Photo/Jeff Chiu)

The relative affordability and portability of new down-sized tablets like the Nexus 7 offer more entry points for tablet consumers, but they present headaches for digital magazine publishers: How do they best reach readers on dozens of different devices with wildly varying screen sizes and processing power?

Why most of you start with iPads

So far, Symbolia, a comics journalism anthology launched late last year by Erin Polgreen and Joyce Rice, has avoided those questions by publishing its first two interactive issues for iPad only.

With just three tablet devices to worry about — standard display iPad, retina display iPad and iPad Mini, all with the same aspect ratio — iOS presented the quickest, cleanest way to reach a large chunk of the tablet audience at launch.

Another point in Apple’s favor: iOS devices are some of the more powerful tablets on the market, ensuring that Symbolia, loaded with pop-ups and HTML animations, would perform cleanly. But as Polgreen and Rice explore expanding to Android, performance and screen size are primary concerns.

“Some of the Androids are very powerful, but some of them aren’t, and I don’t think you get to make a lot of choices in the Android marketplace about who can see your content and who can’t,” said Rice, the creative director. “So it’s definitely a balancing act. I want it to look awesome for everyone, but it’s really determined by the window you’re looking at it through.

That’s a balancing act that Polgreen, the editor and publisher, said Symbolia has no choice but to face. The top request from readers of Symbolia, which also publishes a non-interactive PDF version for those without iPads, is for an Android edition.

“Androids are the primary global operating system,” Polgreen said. “iPads are great. They have a very strong market share, but we’re a global publication. We leave Android out at our own peril.”

Having an Android presence can mean many different things, some of which could be perilous themselves.

Adobe DPS saves production time

The New Republic, which introduced a cross-platform redesign in January, publishes an elegant interactive iPad version of the magazine, with a tappable table of contents, animated section headers and interactive features.

But the version in Google Play’s magazine store is merely a PDF replica of the print magazine. (It also costs a dollar more per issue, but that’s another story.) On a 7-inch Nexus 7, I found it tough to read unless I switched to Google’s magazine text mode. Doing so, however, removes the pleasures of experiencing a magazine layout.

Why the inferior Android product? “It comes down to the simple basic principle of manpower,” TNR’s creative director Dirk Barnett said, adding that his staff of three designers are working on an iPhone version next. “I think we’re just going to sort of pick it off one device at a time once we have it integrated into our workflow process.”

Barnett’s design team uses Adobe’s Digital Publishing Suite to develop and publish the TNR app for iPad. InDesign CS6 introduced liquid layout and alternate layout, tools that drastically reduce the manpower it takes to design for various screen resolutions and orientations.

But until that additional time investment is eliminated altogether, newsrooms will face tough choices about which platforms are worth the sweat and tears required of making tedious adjustments.

PDF replicas predominant on Android

TNR is far from alone in its decision to forgo interactivity on Android devices. Even Popular Science, which has seen 1.6 million unique downloads in Apple’s App Store and was hailed as “king of the hill” on stage by Steve Jobs, still only publishes a PDF replica in the Google Play store.

The Mag+ ecosystem, developed for Popular Science in 2010 and spun out as a separate company in early 2011, initially only supported iPad. It added Android compatibility in June 2011, with two options for publishers wanting to expand:

1) Manually rejigger each page’s iPad layout to fit various Android screen sizes (similar to Adobe’s alternate layout solution, but without the benefit of working within a single document); or

2) Allow Mag+ to scale and letterbox existing layouts automatically for Android devices.

(Full disclosure: I work as a tablet app designer at the Chicago Sun-Times, where we use Mag+ to publish a free Sunday sports magazine for iPad and iPhone. Our other sports apps are designed primarily for iPad with letterboxed Android versions available in the Google Play store.)

Mag+ recently reached a 1,000-app milestone, but just 20 percent of those apps are offered in the Google Play marketplace, Mike Haney, chief product officer, told Poynter. Most of Adobe’s North American clients are primarily focused on iOS, too, said Lynly Schambers-Lenox, group product marketing manager of digital publishing for Adobe.

One reason: workflow restraints like those at TNR. “If the platforms like ours are doing our job well, we make that easy for you to do,” Haney said. And for the most part, manually adjusting a page with either system is easy: Adobe has liquid layout, and Mag+ allows for exporting pages to other InDesign templates that then require mostly minimal adjustments. But these minor adjustments multiplied over dozens of page layouts can become majorly prohibitive.

Another potential reason for publishers’ hesitation to switch from PDFs to native apps on Android: the Google Play magazine store operates differently from Apple’s Newsstand. Whereas Newsstand serves as a hub for apps with the full, optimized functionality of any other app on iPads, Google’s magazine store acts as more of an app itself, facilitating the reading of PDFs.

That can be confusing, as magazine apps exist in the Play store outside the PDF-filled magazine store. At the same time, Haney said, differing expectations of what magazines can do in the Apple App Store versus the Google Play store can provide publishers some leeway when it comes to getting their feet wet with Android by going with PDF replicas. In other words, the competition isn’t as fierce on Android.

Plus, Haney said, the fact that the Google Play and Amazon Kindle stores haven’t developed a way to migrate readers of the PDF magazines to newly developed interactive apps could dissuade publishers who don’t want to lose the audience they’ve built.

Kindle Fire apps still lag far behind Google and Apple in sales, and some reports indicate Android users are less willing to pay for apps than iOS users. If Android users are indeed less likely to buy magazines, that could also be behind publishers’ unwillingness to invest much in them. And that’s a cycle that might not be broken until publishing tools reach a “design once, publish everywhere” solution—something Adobe’s pressing for, Schambers-Lenox said.

Game Informer and The Next Web: two extremes

Haney cited Game Informer as a magazine finding success in both major marketplaces, but even Game Informer’s tablet strategy has some wrinkles.

It publishes a massive iPad edition with Mag+, chock-full of screenshots and embedded video (the October 2012 issue I downloaded had 180 pages and more than 700 megabytes worth of content). The design team, led by creative director Jeff Akervik, also produces an edition for 10-inch Android devices such as the Samsung Galaxy Tab and Note.

For the 7- and 12-inch tablets, though, Game Informer sends its native InDesign files used for print to a team at Google to produce an interactive version with far fewer bells and whistles. “I’m not a real big fan of how vastly different they are from a creative standpoint, but it gets us in the space,” Akervic said of these editions in an email.

It’s definitely a step up from PDF replicas, and workflow restraints mean the Google outsourcing is the only way an interactive version on smaller tablets can exist. “Otherwise, there’d be no way we could physically do that many different designs,” Akervic said. “It’s a tough haul as it is.”

Others publishers, meanwhile, have determined the haul is too tough to include Android at all. The Next Web announced in December that it would stop publishing TNW Magazine for Android. The nature of its content meant it was too cumbersome to adjust layouts and links, founder Boris Veldhuijzen van Zanten wrote in a blog post:

“In theory you simply adjust for a different format and platform and do a new export. But then trouble starts. As one developer put it to us: ‘You make a beautiful magazine for the iPad, and then you dumb it down for Android.’” And once they did so, he wrote, iPad downloads outpaced Android 80-to-1.

Still, if your publication is small and without an overwhelming amount of interactive content, designing for Android should be a relatively small investment. Every reader counts, particularly those on a platform that seems poised to continue growing. Haney recommends building for iOS first, particularly if you’re a small publisher, because of the strong infrastructure already in place.

After that, publishing a standard 1280×800 Android layout will get the magazine on most Android tablets. Buy a Nexus 7—it’s only $199—and see how your content looks on a smaller device. If you don’t build it, they won’t come—and maybe Android users willing to pay for well-designed interactive apps are actually out there, ready to play ball.

Happy designing! (And redesigning… and redesigning… and redesigning… )

source