For a KIOSK application, the user is required to view the entire disclosure before they are allowed to continue. This is a legal requirement, the legal team also turned down an 'I agree' checkbox. We ...
I am interested in research on Walk-up-and-use systems. From what I found so far, Walk-up-and-use systems are described as "system that requires no explicit user training" (hci-hub, FH ...
In our kiosk app, the buttons to proceed are placed on the right of each screen. In one of our input screens, the designer doesn't have enough space to place the button on the right while keeping the ...
What are your thoughts about changing the button label based on what the user has done to the input. For example, for updating an item's price-- once the user enters the 'update page' the button ...
So if my kiosk cannot print or access account info—which are important features—should I introduce a screen to inform the user about that error after sign in (2nd screen in the example below), or ...
I'm designing a kiosk app, we have 2 navigation elements; 1 button for the main menu and 1 for 'back'. So my question is: When should we show the back button? For example, after selecting a menu ...
I am designing an iPad application that will be used in a kiosk. The user will not download the application from the Appstore but will instead walk up to the iPad with the application already running. ...
I have been doing a fair amount of research on Self-Service Technology (SST or kiosks) UX best-practices within a retail environment and how people behave within that context. I would like to expand ...