Click here to Skip to main content
Click here to Skip to main content

Cloud-based Interactive Kiosk and Digital Signage

, 1 May 2013 CPOL
Rate this:
Please Sign up or sign in to vote.
Windows Azure Developer Challenge: Cloud-based interactive Kiosk and Digital Signage

Please note

This article is an entry in our Windows Azure Developer Challenge. Articles in this sub-section are not required to be full articles so care should be taken when voting. Create your free Azure Trial Account to Enter the Challenge.

Introduction

An interactive kiosk is a computer terminal featuring specialized hardware and software designed within a public exhibit that provides access to information and applications for communication, commerce, entertainment, and education. A digital signage is a form of electronic display that shows television programming, menus, information, advertising and other messages.

With the ubiquity of touch-enabled & network-capable devices like iPad, Windows 8/RT, and Android tablets, specialized apps can be used to transform those devices to an interactive kiosk or digital signage.
 

Why Windows Azure?

To maximize the usefulness of an interactive kiosk and digital signage, we have to be able to communicate with those devices to update their contents (i.e., notification, scheduled update, RSS news, etc.) or to receive input from a user (i.e., interactive kiosk). Hence, we need to build our infrastructure to support those scenarios. With cloud, we can build our infrastructure that is scalable and flexible with minimum start up costs.

Windows Azure provides several services such as Cloud services, Virtual machines, Data management (i.e., SQL Database, BLOB, and Tables), Messaging (i.e., Service Bus, and Queues), Web sites, and Mobile Services, that we can use to build our cloud-based infrastructure quickly. Best of all, Windows Azure supports both IaaS and PaaS models, and it is an open platform that allows you to use any languages, tools, and frameworks.

What am I building?

  • Phase 1: Getting Started. Brainstorming and writing this article and apply for the trial account.
  • Phase 2: Build a website. Setting up a SPA and Web API site for content creator.
  • Phase 3: Using SQL on Azure. Link the site from phase 2 with SQL on Azure.
  • Phase 4: Virtual Machines. At this stage, I am not sure if I will need VM capability. I might need only worker roles with messaging and media services to support notification/content updating capability.
  • Phase 5: Mobile access. I will build WinRT interactive kiosk & digital signage app that communicates with Azure infrastructure I build in the previous phases.

Architecture Overview

History

  • May 1st, 2013 : Start writing the article.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Karlkim
Software Developer
United States United States
No Biography provided
Follow on   Twitter

Comments and Discussions

 
QuestionHow to communicate with local devices? Pinmemberdmitrievkv11-May-13 19:14 
It's very interesting idea. But what about of communication with local devices, such as: magnetic/smart card reader, cash validator, fiscal register, ip cam and so on?
AnswerRe: How to communicate with local devices? PinprofessionalKarlkim13-May-13 16:19 
GeneralRe: How to communicate with local devices? Pinmemberdmitrievkv13-May-13 20:21 
GeneralMy vote of 5 PinmemberHugoGonc7-May-13 12:44 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.141216.1 | Last Updated 1 May 2013
Article Copyright 2013 by Karlkim
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid