![]() The set of potential customer requirements is much broader– some kiosk owners want to allow the user to browse anywhere and download any files, etc, while other kiosk owners want to tightly lock down the experience to a small number of supported web pages. While supporting digital signage is reasonably straightforward, providing a true internet kiosk is considerably harder. Similarly, the OS must be configured not to prompt the user for input or show modal dialogs (OS update prompts, etc). Additionally, either the webapp must request a wakelock, or the OS must be configured to let the computer sleep or hibernate. ![]() In this scenario, the browser is typically used to load only a specific website, which itself must be carefully coded not to prompt the user for any input. Supporting this use-case is relatively easy– the browser must be full-screened, and it must avoid showing any sort of prompt, tip, hint, or feature that requires dismissal because there’s no guarantee that a mouse or keyboard is even plugged into the device. ![]() In the Digital Signage scenario, there’s a full-screen webpage rendering and there are no user-accessible input devices– the canonical example here would be an airport’s signage displaying arriving and departing flights and their associated gates. ![]() Digital Signage ( fullscreen) Requirements Today, I take a look at scenarios where there’s either no interactive user (digital signage) or a potentially malicious user (internet kiosks). Browsers get used in many different environments. ![]()
0 Comments
Leave a Reply. |