|By Roy Crisman||
|July 20, 2004 12:00 AM EDT||
Kiosk systems provide a unique set of development conditions and challenges. Whereas most multimedia development produces a software application, a kiosk is a collection of physical, hardware, software, and support systems. This article attempts to look at the entire kiosk project, in hopes that you will have control over most of it.
Design the Process
You already know to do your information architecture (IA), user interface (UI), and usability design for software before the visual layout and software development. You may even have the time, budget, and foresight to do usability testing focused on your target user base with wire frames on paper or with quick software mockups before starting on graphics and code. But for a kiosk, the product is more than an executable file; it is the entire system and process. Besides creating a simple and intuitive UI, you want to simplify the installation, deployment, and support of your kiosk.
Run the entire process through an IA/UI/usability design phase. Create end-to-end use cases; remember to include service and support personnel as users as well as the end user. Consider every aspect you are responsible for or interact with. Don't forget:
- Computer hardware
- The operating system (OS) and third-party software
- Documentation and training manuals
- Online portions
- Administration and configuration components
- UL-type consumer safety testing and certification
- Contracts with third-party vendors
- Support systems
Your initial sketches, charts, and use cases don't have to be incredibly detailed. It is better to realize that these "work products" are just as important to plan, document, and have in source control as the code. Continue to add to them and assign responsibility for the sections as the project grows.
We Control the Hardware
Choose Your Platform
Look at the entire scope of the project to determine which platform(s) you are going to focus on and develop on. It may be helpful to develop for full cross-platform compatibility even if the in-kiosk machine specification is for only one. A cross platform-compliant program can quickly turn into a demo CD-ROM or be viewed by that one client who uses "the other platform." You also want to try to keep your options as open as possible to limit your risk to hardware going out of production. There are several limiting factors on your hardware selection: certain required hardware components, components without drivers or features for a particular OS, sponsorship arrangements with hardware providers, and required software components such as an ActiveX controller for a digital camera.
Use industrial hardware components whenever possible for parts that the end user interacts with. Or, use cheap consumer devices with plenty of spares and a quick replacement process. Most consumer keyboards, mice, trackballs, and joysticks weren't made to withstand children playing on them and drinks being spilled on them daily. I have seen consumer components with impressive technical specs used - and replaced after a year's worth of sub-par performance.
With keyboards there are several options:
- On-screen with a touch-screen monitor: This works best for a small amount of data. It may be more prone to vandalism and require more frequent cleaning, and have a major impact upon the UI/usability and visual design.
- Custom industrial keyboard: This is a more expensive option and probably requires a third-party vendor, may require a Quality Control/Quality Assurance cycle of its own, and allows you to define exactly which keys are available to the user.
- Standard keyboard (industrial or consumer): This keyboard already exists, is less expensive and more thoroughly tested than a custom one, and will require some work with the OS to lock out certain keys and key combinations to protect your system.
Just as you may separate generic code and graphics from specific, it can be helpful to keep user-generated data separate from the OS and application. When the OS hard drive becomes physically damaged, you won't lose any of the previous data. You may even separate the OS from the application.
And We Control the Software
The basic kiosk is just an application program (the Show) running in a box. It probably has an "attract loop" that runs between user sessions, and a time-out mechanism that detects when someone has walked off and returns the application to the attract loop.
The Show (and other kiosk applications) should create at least a couple of levels of logs. A user-interaction log will record the path the user takes through the application in order to data mine for information about how the kiosk is used. Each component may also have its own process or debug log to record the progress through the code, the beginning and finishing of functions and methods, relevant variables and states in the case of trapped errors, interactions between components on the kiosk, as well as attempts to talk to other machines and network processes. These debug logs are indispensable in solving problems if the kiosk does lock up, crash, or error, or even in knowing whether the problem is the code module, the data, the network, or a change to another component having side effects. All log files should be written locally in case off-kiosk communication isn't working and may also be remotely accessed or uploaded to a central location. The data may also be transmitted to a server as it is generated so you can track exactly where a user is, or as part of some multi-user system.
Logging data can be very important for understanding the long-term usage of your kiosks. It also may be important to have archived for historical data: I have parsed through debug logs to discover that the 1.3 release was actually more stable than the 1.2 release - despite the client's convictions to the contrary. Version 1.3 was receiving refocused attention due to the upgrade, showing the weakness of relying on anecdotal evidence of kiosk performance.
The Show and kiosk components have a variety of ways to transmit data depending upon your situation: it can be sent immediately via a direct connection, sent as tasks are completed (at the end of a user session), or queued up in batches to be sent only late at night.
Use audio sparingly and wisely. Audio should work with the entire kiosk, not be something someone just throws in at the end. If you do have audio, consider what can be done to make it more tolerable to any people who work around your kiosk installation. There can be quite a lot of intentional damage to your kiosk installation if it aggravates the people who have to work around it. Even during development, it may not be long before someone who sits near the QA machine asks someone to turn off the sound. (A cheap pair of headphones left plugged into each machine may help ensure office tranquility and allow people to hear the audio when they need to.) Attract loop audio can be especially annoying. Adding randomness and variability to the attract loop audio can greatly increase the experience for people exposed to the kiosk for long periods of time.
Herd animals use deep bass "lowing" sounds because these can travel over greater distances and are hard for predators to pinpoint the location of. Unless you are creating a kiosk about cows, dinosaurs, or the science of sound waves, you should avoid bass, especially when you have a group of kiosks together. This also means you can save money by not buying a subwoofer for the kiosk sound system.
One way to reduce the risk of the effect of downtime due to computer errors is a software or hardware "watchdog" component that reboots the machine if the show quits giving it a signal on a regular interval. A hardware version is more reliable than a software solution because the machine may lock up beyond the ability of the software to restart the system. The watchdog doesn't solve any problems with the kiosk crashing, and any user interacting with the kiosk when it crashes will still have a bad experience; however, if the kiosk is automatically back up and running shortly, it may still give many users a good experience. A kiosk that has crashed or locked up (possibly with sensitive user information left on screen) and sits for hours or days can give a lot of potential users a bad experience.
The kiosk may also require access to configuration settings, utility functions, and the standard OS. It may be helpful to be able to view logs, turn "restricted keys" on the keyboard back on, or to re-enable the cursor on a touch-screen kiosk for development and testing with a mouse. These configuration components and utilities may also be useful as parts of the Console.
The basic idea of the Console is to be able to control any kiosk from anywhere. Technically proficient on-site support is expensive; design and develop as if you will never be able to have a live human configure or support it again. If programmed well, a configuration application may work on kiosk, on a local console machine, and as a remote console, possibly through a Web interface. By making these features usable anywhere, you can change settings or fix problems from around the world or right in front of a suspect kiosk with a wireless device, with the same interface.
The console should be able to make configuration changes to the kiosks, either to a specific kiosk, or broadcast changes to groups of them. It may be useful to be able to control a kiosk by sending it a message that simulates a button push, allowing you to remotely "drive" the kiosk through a workflow.
So, How Are the Kiosks Doing?
One of the most useful features for your remote console is a "heartbeat monitor." (see Image I). The Show can send a "heartbeat" at a regular interval to a remote server, and the heartbeat monitor allows you to view that information. The heartbeat contains a minimal amount of information: kiosk ID, time and date (if the kiosk is scheduled, otherwise skip it and just use the server's time), and maybe what state the kiosk is in. Some useful states are "StartUp" when the machine reboots, "Error" if an error has been trapped and the kiosk is in an error state, "OK" when the kiosk is running fine, or any other modes or states the kiosk has, such as a "Night" or "Closed" mode, or periods of inactivity. The heartbeat monitor then allows to you see what is going on with your kiosks. The minimal heartbeat monitor may just display a green light next to a kiosk name that is okay, a red light next to one that isn't. Without this, you don't have an answer to the question, "How are the kiosks doing?" You can also display more information such as state, timestamps for last error, last restart, last OK ping, etc. With this information, you may end up alerting support staff to things such as the network being down or kiosks needing rebooting, or that maybe something else is wrong because, for example, no has used Kiosk 12 all day.
The heartbeat monitor can also come in handy when you're running QA tests. Your team can monitor the 10 machines across the hall in the QA lab all day instead of walking back and forth only a couple of times a day.
The holy grail of modern kiosk development is remote updating. If you never have to physically intervene with a kiosk in order to change the underlying software, you can greatly decrease the cost of bug fixes, content changes, upgrades, and updates. The console should be able to schedule remote updates and view versioning information for all the kiosks.
The console application may also be able to create and display other kiosk information, including data-mining information. Any information that can be used to chart user interactions, display usage statistics, orders, purchases, media usage, kiosk uptime or downtime, revenue, etc. Image II shows the console application main screen; Image III shows the console "settings" screen.
The Operating System and Supporting Applications
The creation process of the base OS and the installation of any drivers or supporting application programs is just as important to the success of your kiosk as the kiosk show application. Any third-party software required for your kiosk to run should be handled here. This process should be well documented, controlled, and versioned. Small things like the order of installing drivers may be important. Don't upgrade any component without realizing the inherent risk that change can pose. Make changes one at a time with testing, just as you would test major software changes. The more open-ended you can build this process, the better. Work to have a single OS recovery package that will adapt and work for variant hardware.
Quality Assurance, Too
Develop on Your Target Platform and Environment
The more restricted the target hardware/OS/supporting application environment is the more important this is. I know...I've got a snazzy laptop and I don't like the "other" platform either. But it takes only a couple of seconds to test a feature or make a screenshot to illustrate a problem on the target platform. And if I can't control that camera with my preferred system or I can't interface with the database because we don't have a network, the development process will take much longer.
Visual designers should also inspect their artwork on the target hardware displays. Graphics look a lot different in a dark cubicle on a perfectly tweaked 21" flat-screen monitor than they may on an out-of-the-box touch-screen monitor in a brightly lit room. LCD monitors may have problems displaying high-contrast images. Find out that the black, white, and red interface looks like with badly compressed JPG graphics on the kiosk's LCD screen before the client has signed off on the design and all the hardware has been purchased.
Test on Your Target Platform
Independent of your development system, you should have a target platform with controlled and documented hardware, OS, and supporting applications.
Test for the Long Term
Most multimedia application programs are run for only a relatively short amount of time in one session and can be recovered by the user if necessary. But tiny memory leaks can add up over 12 or 72 hours, and may be caused by your application, faulty supporting applications, or even a specific combination of motherboard, audio card, video card, and drivers.
Have at least a basic test constantly running on the target platform. I've been known to utilize "RECORDER.EXE" from Windows 3.1 to record primitive user interactions and then loop them for a week. There are much more sophisticated testing programs available. Target a full week of uptime, but build in a daily reboot if your product allows.
You'll also want to have a real QA process. Because you have a narrow target platform, QA can spend their time on the software functionality, rather than testing for compatibility issues. QA should evaluate and verify the entire process, not just the program, whenever possible, from building the OS, adding supporting applications, installing the application, configuring and deploying, and hardware component replacement.
While you may not be actively involved in supporting the kiosk over the full life of its deployment, there are many things that you can do to aid the support of the system.
Keep a backup of the base OS and of the OS plus the kiosk application at hand at any deployment. This can be used to wipe a troublesome machine clean or to format a replacement machine.
Ralph Waldo Emerson said, "A foolish consistency is the hobgoblin of little minds," but a reasonable consistency is necessary for kiosks. Imagine trying to fix an upside-down kiosk monitor in a remote location and discovering that two of the screws in the bracket holding the monitor require a star screwdriver bit. Work for consistency. Watch for computer hardware consistency - chipsets change in production runs and you never realize the variability in what appears to be the same video card until something doesn't work. Demand consistency from any third-party providers.
Take pictures of the hardware when it is set up correctly, as an illustration. Take pictures of the finished and deployed kiosks for reference later (see Image IV). It may take a long time to figure out remotely that the problem with the kiosk is related to which USB port the digital camera is plugged into.
Keep an adequate supply of replacement hardware on hand at the deployment site. Hardware seems to fail in pairs, but it may be that hardware failures are only noticed and reported by local staff after multiple units have failed. If you have a bug reporting console component that can be used on-kiosk or on a console machine, you will receive more accurate and helpful data than someone trying to decipher a handwritten log a week later. Remember that local personnel are already fully employed; don't count on adding any task to someone's job, even if it will "just take a minute." The security guard doesn't want the added task of shutting down all your machines every night any more than you do. Make sure any contracts and agreements define who is responsible for and who pays for upkeep, cleaning, checking on the physical system (blown monitors) and theft/vandalism. How hard or easy it is to support your kiosk systems is going to depend upon how well you are able to document, control changes, and simplify systems during development.
Kiosk systems can be rewarding to develop, allowing for far greater control over the system and the ability to push the limits of multimedia development. A kiosk is so much more than the interface the user interacts with, and thus requires more planning and development than typical multimedia software.
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform. In his session at @ThingsExpo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and shared the must-have mindsets for removing complexity from the develo...
Jul. 26, 2016 02:00 AM EDT Reads: 1,297
SYS-CON Events announced today that MangoApps will exhibit at the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. MangoApps provides modern company intranets and team collaboration software, allowing workers to stay connected and productive from anywhere in the world and from any device.
Jul. 26, 2016 01:45 AM EDT Reads: 1,296
The IETF draft standard for M2M certificates is a security solution specifically designed for the demanding needs of IoT/M2M applications. In his session at @ThingsExpo, Brian Romansky, VP of Strategic Technology at TrustPoint Innovation, explained how M2M certificates can efficiently enable confidentiality, integrity, and authenticity on highly constrained devices.
Jul. 26, 2016 01:30 AM EDT Reads: 984
The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Digital Transformation, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportuni...
Jul. 26, 2016 01:15 AM EDT Reads: 2,517
In today's uber-connected, consumer-centric, cloud-enabled, insights-driven, multi-device, global world, the focus of solutions has shifted from the product that is sold to the person who is buying the product or service. Enterprises have rebranded their business around the consumers of their products. The buyer is the person and the focus is not on the offering. The person is connected through multiple devices, wearables, at home, on the road, and in multiple locations, sometimes simultaneously...
Jul. 26, 2016 12:45 AM EDT Reads: 629
“delaPlex Software provides software outsourcing services. We have a hybrid model where we have onshore developers and project managers that we can place anywhere in the U.S. or in Europe,” explained Manish Sachdeva, CEO at delaPlex Software, in this SYS-CON.tv interview at @ThingsExpo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Jul. 26, 2016 12:00 AM EDT Reads: 1,540
"We've discovered that after shows 80% if leads that people get, 80% of the conversations end up on the show floor, meaning people forget about it, people forget who they talk to, people forget that there are actual business opportunities to be had here so we try to help out and keep the conversations going," explained Jeff Mesnik, Founder and President of ContentMX, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Jul. 25, 2016 11:15 PM EDT Reads: 1,310
From wearable activity trackers to fantasy e-sports, data and technology are transforming the way athletes train for the game and fans engage with their teams. In his session at @ThingsExpo, will present key data findings from leading sports organizations San Francisco 49ers, Orlando Magic NBA team. By utilizing data analytics these sports orgs have recognized new revenue streams, doubled its fan base and streamlined costs at its stadiums. John Paul is the CEO and Founder of VenueNext. Prior ...
Jul. 25, 2016 11:15 PM EDT Reads: 2,014
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo Silicon Valley Call for Papers is now open.
Jul. 25, 2016 10:00 PM EDT Reads: 2,505
The IoT is changing the way enterprises conduct business. In his session at @ThingsExpo, Eric Hoffman, Vice President at EastBanc Technologies, discussed how businesses can gain an edge over competitors by empowering consumers to take control through IoT. He cited examples such as a Washington, D.C.-based sports club that leveraged IoT and the cloud to develop a comprehensive booking system. He also highlighted how IoT can revitalize and restore outdated business models, making them profitable ...
Jul. 25, 2016 08:30 PM EDT Reads: 1,940
With 15% of enterprises adopting a hybrid IT strategy, you need to set a plan to integrate hybrid cloud throughout your infrastructure. In his session at 18th Cloud Expo, Steven Dreher, Director of Solutions Architecture at Green House Data, discussed how to plan for shifting resource requirements, overcome challenges, and implement hybrid IT alongside your existing data center assets. Highlights included anticipating workload, cost and resource calculations, integrating services on both sides...
Jul. 25, 2016 08:00 PM EDT Reads: 1,979
Big Data engines are powering a lot of service businesses right now. Data is collected from users from wearable technologies, web behaviors, purchase behavior as well as several arbitrary data points we’d never think of. The demand for faster and bigger engines to crunch and serve up the data to services is growing exponentially. You see a LOT of correlation between “Cloud” and “Big Data” but on Big Data and “Hybrid,” where hybrid hosting is the sanest approach to the Big Data Infrastructure pro...
Jul. 25, 2016 07:30 PM EDT Reads: 1,893
"We are a well-established player in the application life cycle management market and we also have a very strong version control product," stated Flint Brenton, CEO of CollabNet,, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Jul. 25, 2016 07:15 PM EDT Reads: 1,798
We all know the latest numbers: Gartner, Inc. forecasts that 6.4 billion connected things will be in use worldwide in 2016, up 30 percent from last year, and will reach 20.8 billion by 2020. We're rapidly approaching a data production of 40 zettabytes a day – more than we can every physically store, and exabytes and yottabytes are just around the corner. For many that’s a good sign, as data has been proven to equal money – IF it’s ingested, integrated, and analyzed fast enough. Without real-ti...
Jul. 25, 2016 07:15 PM EDT Reads: 1,024
I wanted to gather all of my Internet of Things (IOT) blogs into a single blog (that I could later use with my University of San Francisco (USF) Big Data “MBA” course). However as I started to pull these blogs together, I realized that my IOT discussion lacked a vision; it lacked an end point towards which an organization could drive their IOT envisioning, proof of value, app dev, data engineering and data science efforts. And I think that the IOT end point is really quite simple…
Jul. 25, 2016 06:30 PM EDT Reads: 998
A critical component of any IoT project is what to do with all the data being generated. This data needs to be captured, processed, structured, and stored in a way to facilitate different kinds of queries. Traditional data warehouse and analytical systems are mature technologies that can be used to handle certain kinds of queries, but they are not always well suited to many problems, particularly when there is a need for real-time insights.
Jul. 25, 2016 06:15 PM EDT Reads: 1,760
Unless your company can spend a lot of money on new technology, re-engineering your environment and hiring a comprehensive cybersecurity team, you will most likely move to the cloud or seek external service partnerships. In his session at 18th Cloud Expo, Darren Guccione, CEO of Keeper Security, revealed what you need to know when it comes to encryption in the cloud.
Jul. 25, 2016 06:00 PM EDT Reads: 2,444
We're entering the post-smartphone era, where wearable gadgets from watches and fitness bands to glasses and health aids will power the next technological revolution. With mass adoption of wearable devices comes a new data ecosystem that must be protected. Wearables open new pathways that facilitate the tracking, sharing and storing of consumers’ personal health, location and daily activity data. Consumers have some idea of the data these devices capture, but most don’t realize how revealing and...
Jul. 25, 2016 06:00 PM EDT Reads: 2,079
You think you know what’s in your data. But do you? Most organizations are now aware of the business intelligence represented by their data. Data science stands to take this to a level you never thought of – literally. The techniques of data science, when used with the capabilities of Big Data technologies, can make connections you had not yet imagined, helping you discover new insights and ask new questions of your data. In his session at @ThingsExpo, Sarbjit Sarkaria, data science team lead ...
Jul. 25, 2016 03:45 PM EDT Reads: 971
Extracting business value from Internet of Things (IoT) data doesn’t happen overnight. There are several requirements that must be satisfied, including IoT device enablement, data analysis, real-time detection of complex events and automated orchestration of actions. Unfortunately, too many companies fall short in achieving their business goals by implementing incomplete solutions or not focusing on tangible use cases. In his general session at @ThingsExpo, Dave McCarthy, Director of Products...
Jul. 25, 2016 03:30 PM EDT Reads: 1,703