If you’re developing a kiosk application you’ve probably wondered what technology you should use.
The two most common options are creating a website or a native application. In this article we’ll focus on the benefits of creating a native kiosk application.
Our developers have been creating large-scale, unattended payment applications for many years now and the following are the reasons we choose to develop our kiosk applications as a native application (typically in .NET WPF).
KioskSimple makes it a breeze to convert any PC or tablet running Windows 8 into a self-service kiosk. The fastest way to get your kiosk up and running is to create a website with all of your kiosk content and let KioskSimple “lockdown” the website on your kiosk. Checkout the video below to see just how easy it is to put your website on a self-service kiosk running Windows 8.
How much does it cost?
There is a one-time license fee of $199/kiosk with volume pricing available.
In this article I’ll explain how to disable the Windows Sleep and Hibernation Power Options directly from your kiosk application. Imagine the scenario where your kiosk goes to sleep and potential customers see nothing but a black screen. Many customers will assume the kiosk is out of order and keep right on walking. To make matter worse, when the user touches the screen they’ll be greeted by a Windows login prompt and chances are they won’t know the password. Continue reading “Disabling Windows Sleep and Hibernation From Your Kiosk Application”
In this article I’ll explain how to temporarily disable the built in Windows screen saver from your kiosk application. If you’ve created a native Windows application (i.e. .NET WPF) to run on your self-service kiosk you probably don’t want it to be interrupted by the Windows screen saver. Sure you could go to the screen saver settings and disable the screen saver completely but then you’d have to do that on ever single kiosk. It would be more convenient to temporarily disable the screen saver only while your kiosk application is running. Continue reading “Disabling the Windows Screen Saver From Your Kiosk Application”
Adding a webcam to your kiosk application can go a long way to improve the security of your kiosk. In the case of disputed credit card charges (i.e. chargebacks) it can help to have a picture of the customer swiping the card in question. One of our main goals with KioskSimple was to make it really easy for kiosk application developers to integrate popular kiosk devices, like webcams, into their kiosks. The KioskSimple developer API supports integrating a webcam into your website or .NET WPF kiosk application and we have code examples to get you started. Continue reading “Integrating a Webcam Into Your Kiosk Application”
We really like the Magtek credit card readers and wanted to make them simple to integrate with your kiosk application using our KioskSimple developer-friendly API. Credit cards are clearly the most popular form of payment being accepted by payment kiosks today and with just some minor code changes your kiosk application can begin accepting credit card payments also. The KioskSimple developer API supports integrating Magtek credit card readers into your website or .NET WPF kiosk application and we have code examples to get you started. Continue reading “Integrating Magtek Credit Card Readers Into Your Kiosk Application”