own approach • Wasted development effort • Users face inconsistent interaction models We can learn from the desktop platform • GUIs faced similar problems 3
For web-based PD applications • A widget represents an interactive feature. – Is represented by a class in an object-oriented programming model. – Applications instantiate widgets and receive interaction events via a callback function 9
entry, Download, Upload, Check-in • Supports various input mechanisms – SMS, Bluetooth naming, QR codes, email, touch (with limitations) • Automatically generates GUIs for desktop and mobile devices • User identification in input events • Asynchronous events • Graphical representations for widgets • Client and server application models
display applications • Web-based – “Easy” development • Various widgets – Supporting diverse interactions • Multi-user – Supporting simultaneous, shared interactions • Multiple input mechanisms – From web-based, QR codes, to SMS • Async input – To support offline interactions and various application models 15
coordination between displays Android/iOS “Open-in”/”Share to” Public display near you PD App: users upload content that they can later request the display to show Interactive marketing How to effectively communicate interactivity Guidelines for content creation Wordpress plugin for content creation “Place” representations Who’s around app 17