Home > Adobe, Digital Publishing Platform, InDesign > DPS Webinar Notes: Part 1

DPS Webinar Notes: Part 1

Digital Publishing Overview & Preparation

This is just a high-level overview of the overall process…

  • Creative Suite CS 6 [InDesign] + DPS Services [Produce | Distribute | Monitize | View | Analyze]

Multiple Platforms

  • Multiple target device, including browser based sharing for those not on tablet

Workflow Automation

  • InDesign -> Folio Produced SDK Automated Workflow -> Digital Publishing Suite Services

Analytics

  • Optimize editorial and advertising content
  • Site catalyst by Omniture

Getting Started

  • Just need InDesign CS 5, 5.5 or 6
  • And free Adobe ID

New Folio

  • Single or dual orientation
  • Cover Preview – Seen in library/bookshelf
  • Recommended to use multiple Adobe IDs for multiple publications when creating content

Branded Application (App Builder)

  • Make Branded Viewer
  • Create App… command
  • Specify Icons for App
  • Options for navigation tool bars
  • Social sharing options are setup here
  • [Sign up for Developer Account with Apple]
  • Fill out certificate information
  • Create app – All information sent to server that builds the .ipa (app file) that can be installed/sideloaded on ipad
  • Add locally to ipad (through itunes)  for testing
  • “publish’ in folio producer – File is moved to distribution serverce (enterprise solution)

Complexities in Building Content (Realistic Timeline)

  • Month 1 : Basic configuration & Setup, Outline Internal processes & schedules.
  • Month 2: Initial app development, content lock & App QA
  • Month 3: App submission & Approval (2 weeks), App launch
  • Going forward: Subscriptions & bundles, plans for upgrade

DPS Test Plan

  • Verify application compatibility
  • Verify & test content
  • Test in-app purchases
  • Ensure analytics are working
  • Test enterprise features
  • Test application updates

Create Security Certificate

  • Apple & Android require all apps to be digitally signed with a certificate whose password is held by the application’s developer
  • The certificate is used to identify the author of an application
  • Apple requires certificates be generated by “certificate authority” (apple)
  • Android allows self-signed certificates by a standard Java library
  • Apple requires dev versions to be signed with a “mobile provision’ file that limits the number of devices they can be run on (to avoid side-loading)
  • Apple allows signing apps with Enterprise certificates to remove this limitation
Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: