Screens Cloud Service
summary
Screens Cloud packages AEM Sites content into an offline-capable player that downloads a v3 manifest via smartsync, avoids re-downloading existing assets, and supports gapless playback and fast local response for touch and triggers. Delivery separates a content provider (AEM) from a services provider (Adobe IO API gateway and microservices) for registration, bulk assignment and monitoring; device groups scale to ~10,000 each and deployments routinely handle hundreds of devices per day. Built players run in an iframe shell with local package management and health logging.
AI-written summary · about
chapters (7)
- 0:00Introduction to Screens Cloud
- 1:48Hybrid experiences with Sites
- 5:22Key differences web vs digital signage
- 10:39Authoring and delivery approach
- 14:09Offline mode and SmartSync
- 18:22Screens Cloud architecture
- 26:30Key takeaways and summary
related talks
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
02mAEM Shorts: Modernizing Your AEM Implementation with Cloud Service
01h 00mBuilding next gen composable services with Experience Manager
02mAEM Shorts: Content Reuse and Omnichannel Delivery with AEM
54mAdobe Experience Manager Rock Star: The Headless Challenge
48mContext, multi-device and the future of TV in the browser
38mSeamless Integration of Experience Manager Assets with Applications
10mEscaping tabs with progressive (web) apps