own approach • Wasted development effort • Users face inconsistent interac(on models We can learn from the desktop pla?orm • Faced similar problems in the beginning Motivation 3
• For web-‐based PD applica(ons • A widget represents an interac(ve feature. – Is represented by a class in an object-‐oriented programming model. – Applica(ons instan(ate widgets and receive interac(on events via a callback func(on PuReWidgets 9
entry, Download, Upload, Check-‐in • Supports various input mechanisms – SMS, Bluetooth naming, QR codes • Automa(cally generates GUIs for desktop and mobile devices • User iden(fica(on in input events • Asynchronous events • Graphical representa(ons for widgets • Client and server applica(on models Features
lower the barrier to public display applica(on development • Such toolkits will be crucial for widespread crea(on of new public display applica(ons. • Focus on making it easy to explore interac(ve features in applica(ons Conclusion 15