A practical example
A kiosk receives no confirmation after sending a request. Showing a success screen would mislead the visitor; repeating the request could create a duplicate. Define a pending state and a reconciliation path.
Start before the first tap
Why does someone approach the kiosk? What information do they have, and what do they expect to leave with? These questions help define the beginning and end of the journey. Physical placement, readability, accessibility and the time available to make a choice all shape the interface.
Know where completion is confirmed
A successful screen transition does not necessarily mean a business operation succeeded. Identify the system or device that confirms the relevant action and define how the interface represents pending, completed and unsuccessful states. This helps prevent a user from leaving with the wrong understanding of the result.
Design for interruption
People hesitate, step away and change their minds. Connections and devices can also become unavailable. Define what happens when a session times out, how information is cleared and whether an action can safely be retried. Recovery behavior is part of the product experience, not an invisible technical detail.
Validate on the target setup
A desktop demonstration cannot establish how a kiosk will behave with its actual screen, peripherals, network and users. Test representative journeys on the intended configuration, including difficult and interrupted cases. The evidence should cover both the visitor’s understanding and the operation behind the screen.
Use this in your next project discussion
| Question | Why it matters | What to establish |
|---|---|---|
| Where is completion confirmed? | Screen transitions are not proof. | Identify the authoritative system. |
| What survives a timeout? | A visitor may walk away. | Define session cleanup. |
| Can we retry safely? | The first request may have succeeded. | Define duplicate prevention. |
Limitations and tradeoffs
Kiosk behavior depends on the selected hardware and the connected workflow. Offline synchronization, retry and recovery rules must be tested against that environment; no universal availability claim is made.