The Dangers of Non-Kiosk-Specific Software
For Your Eyes Only
By Stephanie Kropkowski, Director of Marketing and Sales, KioWare.
Most major browsers offer a free and easy-to-use kiosk mode version which displays the application full screen. However, there can be unexpected costs such as kiosk downtime, loss of data, a change in kiosk settings and a loss in ROI. When deploying a browser based kiosk, no matter what the kiosk’s intended purpose, you should be aware of the detriments of running your browser in kiosk mode instead of using kiosk-specific system software.
A number of different key combinations could open a new browser window, where users could bring up an inappropriate, or even competitive, website. Whatever is opened renders your kiosk useless for the intended purpose, leaking money from your investment. Kiosk software, such as KioWare, offers configurable keyboard filtering, allowing you to select which keys you can block from users.
Other key combinations can delete the kiosk screen all together, allowing users to gain full access to the OS and desktop. If the kiosk is connected to the company network, it’s even possible to gain access to confidential information. Users can also change the kiosk settings completely, resulting in downtime and requiring you to re-configure the kiosk. However, kiosk software locks the browser so that users are unable to gain access to the OS and desktop.
Additionally, running your browser in kiosk mode does not usually return the kiosk to the start page at the end of the session. A kiosk is more likely to be used if some kind of attract screen is capturing attention, rather than a static page that the last person viewed. Even worse, any information entered by the last user will remain onscreen. Worse still, cookies, cache and clipboard information aren’t cleared through your browser’s kiosk mode. All of that information is available to anyone using the kiosks. Kiosk software resets the application to the start page and simultaneously clears all of the previous user history.
Tuesday, November 2, 2010