• Focus more on the horizontal scrolling rather than vertical. This is because UI elements Will surely end up at the bottom of the page if it’s designed vertically. Also any chance for eye-catching animation between pages can be taken advantage of.  There’s nothing interesting about the vertical scroll on the phone, it’s usually there for lazy loading utility and infinite lists.  This also has some implications for using the entire screen. Barring any specific application, which may require lazy loading or infinite loading, most applications will take the user to an entire screen, or as much of the screen as is visible within the distance that one normally interacts with the kiosk.

Rules of thumb:

  • The top 4 inches of the screen are a no-go for interaction and UI – save it for navigation.

• The bottom quarter is also a no go for interaction and UI – it’s awkward to manipulate on a large, vertical screen.

• One call to action per screen.

• Easy to understand: where user came from, where they can go next, and how to get back to where they were. – Web UX principals.

• For more complex applications, where a more customized UI is necessary, make the default UI elements fixed to the right of the screen. This is because 95 or more percent of users will be right-handed. This may seem like an issue for accessibility, but being left-handed is not a disability, and in any marketing situation or UX usability test, 95% adoption rate is a sure thing.  Also there is no standard interaction element for changing the side of the controls, and Any development along these lines should be saved for after the first round of feedback so we can determine the actual positive benefits that ‘handedness’ will play in design before we commit to developing.  We will explore ‘handedness’ for touchscreens more closely in later articles.