Digilific

 i-content Kiosk 

Acronym warning!!

Goals

• Separation of concerns..
• Anyone can amend..
• Flexibility on-site..
• Make it a platform
• Abstract the metrics away.. 
• Easy to deploy..
• Maintainable!

Can run indefinitely without crashing!

Kiosk 'Player' app

Metrics

Adaptor

View 

Buffers

Transition

Manager

Message

Bus

Kiosk 'Content' Bundle

App Config

HTML / JS / CSS

Message Bus

Kiosk Player && Kiosk Content

"Player" Concerns :

• Loading/unloading content safely
• Manage page transitions
• Metrics abstraction
• Runtime configuration

"Content" Concerns :

• Look good
• Feel good / performant
• Easy to edit (by amateurs)

Single Page App vs Multi page

SPA's have a risk of being harder to keep 'zombie free'

Editing content should be easy, abstract away the noise!

We don't restrict from any approach!

We do want to keep the entry to editing as LOW as possible!

MPA makes more sense

MPA Approach

• Uses IPC message emitter to talk to 'player'
• Two buffer web-view
• Navigation events (e.g. href clicks) prepare the next page in the unused buffer. 
• Isolates memory by dumping old page content completely
• Slick translation to show next page to the user.