Presented at 3|SHARE's EVOLVE'14 - The Adobe Experience Manager Community Summit on Wednesday November 19th, 2014 at the Hard Rock Hotel in San Diego, CA. evolve14.com
6. 6
•Smart phone use continues to grow
•Table use continues to grow
•Mobile apps and downloads continues to grow
•Mobile App usage continues to outpace mobile web
MOBILE TRENDS
7. 7
•Tablets: Time spent per app session is 4X longer than web
•Smartphones: Time spent per app session is 2.5X longer than web
MOBILE TRENDS
Tablets vs. Phones
•
Phone is go to device for most users
•
Tablets provide better user experience and results in longer user sessions
•
Tablet users spend more
10. 10
MOBILE APP TYPES
Utility apps
Content-centric apps
Device-centric: Casual gaming or transaction-based apps that rely heavily on device features
Connected tasks: Transaction and task oriented apps such as mobile banking
Content-focused: Consumption of content, little/no data entry
11. 11
ADOBE® DIGITAL PUBLISHING SUITE (DPS)
“Create, distribute, monetize, and optimize engaging content and publications for mobile devices.”
Brand & retail affinity
Sales enablement
High-value customer communication
Magazines
13. 13
Pros:
•
Highly designed content that can be very engaging and interactive
•
Creatives have a great deal of freedom
Cons:
•
Slow – custom layout for each article and orientation
•
Multiple files for different target devices
•
Requires InDesign expertise
DPS
InDesign Workflow
14. 14
Pros:
•
Rapid development using templates
•
Automated creation of multiple formats
•
Easy content reuse
•
Content is fully managed
•
Low barrier to entry for users
Cons:
•
Pixel perfect/complex layouts are difficult
AEM + DPS
AEM Workflow
16. 16
•Single authoring environment for all channels
•Reuse skillsets to manage and develop sites and apps
•Reuse assets across channels and devices
•Develop, manage and analyze mobile apps
•Reduce costs, increase consistency improve brand loyalty
AEM 6.0 APPS
Optimized multi channel content delivery
+
18. 18
AEM APPS
PhoneGap Enterprise (PGE)
•
Application Command Center
•
single user interface for managing all aspects of an app’s lifecycle
•
App Update Management
•
update apps directly with app store
•
App Content Authoring
•
Non-developers can easily create and update content using a touch based, WYSIWYG, drag and drop interface
•
PhoneGap build integration
•
Build apps without a development environment
•
Adobe Mobile Services Analytics integration
•
Track and report app usage
•
PGE Content Viewer
19. 19
AEM APPS
Digital Publishing Suite (DPS)
•
5.5
•
InDesign Server Integration introduced
•
5.6
•
DPS Integration Introduced
•
6.0
•
Multi Folio Support via Livecopy
•
Touch Publication Console
•
6.0 Mobile Apps Feature Pack (Nov/2014)
•
Adobe Content Viewer (ACV) Support
•
6.1 (2015)
•
…
*DPS Next
20. 20
AEM APPS
Digital Publishing Suite (DPS)
•
SPEED
•
Non-developers can easily create and update content using a touch based, WYSIWYG, drag and drop interface
•
Quickly and easily mange content targeting tablets and smartphones via the Publications Console
•
View content directly in Adobe Content Viewer (ACV) from AEM, by- passing Folio Producer
•
COST
•
Reduce multichannel development and distribution costs by reusing existing content and skills
•
CONSISTENCY
•
Ensure content and branch consistency across channels and devices
21. 21
DEMO
DPS Integration
•
Publish AEM Folio
•
Create and Assign DPS Cloud Service to a Folio
•
Upload Folio from AEM to Folio Producer
•
View in Folio Producer
•
Multi Folio Support
•
Create Live Copies for multi-device Folio
•
ACV preview
23. 23
KEY TAKEAWAYS
1
DPS as a mobile channel for AEM content
2
Developers continue using their AEM skills
3 Authors continue to manage content the AEM way
24. AEM + DPS
Adobe InDesign Server (IDS) Integration
•
InDesign
•
design page layouts for print and/or digital distribution.
•
InDesign Server (IDS)
•
Scripting engine service
•
automated document creation and processing based on InDesign.
•
Uses extendscript (similar to javascript)
•
AEM integration with InDesign Server 6.0 or higher
•
proxy worker to communicate with the IDS
•
scripts stored in AEM, pushed to IDS to execute
•
scripts can GET and POST back to AEM
•
Used via workflow process steps
•
Uses
•
extract metadata and generate various renditions for DAM
•
merge AEM content into InDesign templates
34. 34
•
ContentSync for AEM content export
•
static renderings
•
link rewriting
•
transformations
•
Folio linked to configurations via property dps-exportTemplate
•
ContentSync Configs
•
dps-folio configuration transforms content in <article>.folio
•
dps-HTMLResources configuration transforms AEM content into HTMLResources.zip
AEM + DPS
ContentSync configuration for DPS export
35. 35
•
Introduced in CQ 5.4
•
Render content for export based on content handler configs
•
Many OOTB handlers
•
Supports custom handlers
•
Export strategies
•
Short lived via templates (DPS)
•
Long lived (PGE)
AEM + DPS
ContentSync for Mobile
36. 36
DEMO
Folio Aware Component : Scaling Image Component
Problem: Content is not optimized for all devices
•
iPad targeted assets work on a phone but can we do better?
Solution: Folio Aware Component
•Ex. Scaling Image Component : Server side scaling and quality adjustment
37. 37
DEMO
Folio Aware Component : Scaling Image Component
Details: Servlet to render to target size and quality <RESOURCE_PATH>.img.<FOLIO_SIZE>.<QUALITY>.<EXTENSION>
Component: extension of foundation image component
ContentSync Export handler: dpspages
{
IF component in Folio
THEN change rendering based on Folio metadata
ELSE default rendering
}
41. 41
DEMO
Folio Creation and Content Reuse
Problem: Andrew issued challenge
“Can you publish your slides as a DPS App”
Solution: Accept challenge
•Enable sub assets in DAM update assets workflow
•Create a workflow that creates a folio and articles from the ingested power point slides
•Publish the created folio
•View in Adobe Content Viewer
42. 42
DEMO
Custom ContentSync Handler
Problem: Where is my content?
•Not all content is exported automatically
Solution: Custom ContentSync handler
•Create a custom handler to export content as needed
43. 43
DEMO
Custom ContentSync Handler
Details: Simple Native video component
Component: extension of foundation video component
ContentSync Export handler: custom-your-name-here
•
implement com.day.cq.contentsync.handler.ContentUpdateHandler
•
[extend com.day.cq.contentsync.handler.AbstractSlingResourceUpdateHandler]
•
Implement public boolean updateCacheEntry(ConfigEntry configEntry, Long lastUpdated, String configCacheRoot, Session adminSession, Session userSession){
{
FOR each resource under pages jcr:content
IF resourceType IN handledResourceTypes
THEN render/copy/update into ContentSync cache
}
44. 44
TIPS & TRICKS
•
Use RWD & AWD
•
Manage folio size
•
Embrace simplicity
•
Look for existing and new DevNet articles
•Preview /Debug
•In AEM
•Of file system
•On Device
•Logging
•Increase logging of com.adobe.cq.media
•Redirect DPS_FP_EVENTS & DPS_CQ_EVENTS to dps.log
45. 45
KEY TAKEAWAYS
1 DPS as a mobile channel for AEM content
2
Developers continue using their AEM skills
3
Authors continue to manage content the AEM way