Skip to content
Interface language: English
Design / Signal

Shared terminals: the screen needs a fresh start after a customer leaves

Design a visit on a shared terminal: a clear start, end, inactivity warning and return without the previous person's data, with a concrete acceptance test.

Article language: English

Aeneia world concept: a designer tests movable wall modules and benches on open terraces overlooking the water.
In this article

The screen in a materials showroom still displays a selection made by the previous customer. A new person presses "Next" and sees someone else's email address. The terminal carries on smoothly. The problem is that it is carrying on the wrong visit. A button leading to the home page is not enough to end the entire journey.

A shared station differs from a private phone above all because its users change. Someone may leave without signing out, leave a download window open, or return shortly after another person has taken their place. The design should establish in advance what a beginning means, what ends a visit and how the next person can recognize that the station is ready for their own task.

Consider a fictional fabric showroom. At the terminal, a customer can assemble samples, send themselves a link to the selection and download a summary. No account is required. The customer needs to finish preparing a set, and the staff need to receive the correct request. But the device belongs to the showroom, so behaviour convenient on a personal computer can cross the boundary between visits here.

The start should make clear whose work this is

The first screen should provide a recognizable beginning to a new task. The showroom name and a "Prepare a sample set" button are useful if the previous selection does not return one step later. In a test, open the catalogue after a visit has ended. Check selected colours, the email field, the last search and the summary. A welcome screen alone may hide retained state instead of separating it.

Briefly explain the nature of the station on entry. "This is a shared screen. Send the set to your own address and end your visit when you are finished" says more than a padlock symbol alone. The user should know where to find the result later before providing contact information. If data remains in the showroom's case record, the closing message must not imply that every trace of the request has been deleted.

Limit data to what this task needs. In our example, an email address serves to receive the set; a surname or company details are not necessary merely to select fabrics. If staff need additional information to prepare samples, name its purpose. A long form on a public screen increases the time during which people standing nearby may see entered data.

The sending summary needs its own scope. A full address helps catch a typo before confirmation, but it need not remain on screen until an automatic reset after the action is complete. A design can show a limited confirmation while preserving a separate correction path for someone still using the station. Check both moments: the customer must recognize the address for receiving the set, while a passer-by should not see an unnecessary full copy of the data. Merely reducing the font size does not resolve this relationship.

Design a way to take the result to a personal device. It may be a message with a link or another agreed method the customer understands. Sharing a link (in Polish) itself requires an access decision: can anyone holding the address open it, or only a specified person? Ending the terminal visit and the validity of the received link are separate conditions.

The help button should lead to real assistance at the venue. A customer at a shared screen need not be able to diagnose a browser problem. "Ask the person at the sample station" may be more useful than an elaborate technical form. The showroom team, in turn, needs a way to enter staff mode that does not leave its access available to the next customer.

What must happen after a visit ends

After preparing a selection, the customer presses "Send the set to my address". First establish the result of that action. A confirmation after a form (in Polish) should reflect what the system has actually accepted. On a shared device, another decision follows: when is it safe to remove from the screen material needed to correct an error?

If the address is invalid, the customer must still be able to correct it during the same visit. If the result of sending is unknown, the screen should neither announce delivery nor start a new case from scratch. A request may have been accepted even though no response reached the terminal. The state of the visit and the state of sending therefore need separate labels.

Also prepare for a person leaving after pressing send, with the response arriving only after the visit has ended. Acceptance of the set must still concern the earlier case. But a late message must not redisplay the previous customer's data to someone who has just begun their own selection. The design must therefore allow a visit to end with a result pending and provide later confirmation through the appropriate channel. A clean screen for a new visit is no reason to lose the connection between the earlier request and its result.

After confirmation, show a clear "End visit" action. This differs from "Return to catalogue", which may let the same person continue browsing. If both actions look identical, a customer can leave believing they have finished while the application retains their selection for the next visitor. The button name should match its actual effect.

MDN describes the Clear-Site-Data header as a signal to remove specified kinds of browsing data. The scope depends on the directives used; this is a different mechanism from simply navigating to the start screen.

Describe the result of ending in ordinary words: the previous person cannot reopen their data from this station without following the proper access path, and the new person cannot see their working set. The implementer chooses the application, browser and device mechanisms. The screen should show a confirmed result of those actions, not promise it merely because an attractive welcome screen has appeared again.

Downloading a summary introduces another place to include in acceptance. A file may already be outside the page itself. A customer seeing "Download" may assume they are taking the document with them, even though they are using the showroom computer. The label or description should reveal where the result will go. Sometimes sending it to a personal device will be a better route.

Google Chrome Help on Incognito explains that downloaded files remain on the device after that mode ends. Private mode alone therefore does not resolve the entire handling of materials.

Walk through the same task with printing if the terminal offers it. The printout should reach the right person, and the screen still needs to end the visit after printing. Do not treat the movement of paper as confirmation that the application session has ended. In our showroom, printing could be limited to a non-personal list of samples, with contact details kept elsewhere.

Aeneia conceptual photography

Aeneia Design can discuss the design of these screens and states and agree the scope of acceptance criteria. One actual journey is a useful starting point: what the customer selects, how they receive the result and when they hand over the station. Device configuration and confirmation of data removal must be assigned to the appropriate part of implementation.

The person has left, but the application is still waiting

Not everyone will press the end button. Someone hears their name, leaves to speak to staff or simply assumes a finished set means the visit is over. The inactivity mechanism must handle precisely this journey. Its job is not to race the customer against the clock, but to leave the station in a recognizable state after an interrupted visit.

WAI's explanation of WCAG success criterion 2.2.1 describes turning off, adjusting or extending time limits and specified exceptions. It is a design reference, not proof that the entire terminal conforms.

When setting the time, account for work that looks like inactivity to the application. A customer may read a fabric description, compare a sample beside them or wait for a companion's answer. No screen press does not necessarily mean they have left. The warning should make the consequence clear and provide a simple way to confirm continued work.

In the showroom, a message might say: "We will shortly end this visit and hide the selection on this shared screen. Are you still using it?" Clear actions must follow, such as "Continue my selection" and "End visit". Do not add another confirmation after every confirmation. The user needs time to decide, not a separate test of reflexes.

The continue button does not recognize the person. Someone who has just approached an abandoned terminal can press the same button. If a visit contains data that needs separation, "I am still using it" alone should not prove that it can be shown again. Choose the expected behaviour according to the type of information and the available way to confirm access. In our showroom, a selection of general fabrics has a different significance from an already entered contact address.

During a short interruption, a non-personal selection might be allowed to continue, while reuse of contact information is handled separately. Or the design could require every ended visit to start again, with the result recoverable only through a previously sent link. The customer would then need to repeat some selections. Show that consequence before ending the visit, so they do not discover it only on returning. It makes no sense to promise both convenient recovery without any confirmation and certainty about who has approached a public screen.

Test the warning with a keyboard and screen reader as well. A person who has only just heard the beginning should not lose the ability to act because a short countdown has ended. Website accessibility (in Polish) needs to be checked here in the interrupted state, including button placement and actual conditions at the device.

A prototype on a desk will not reveal every difficulty at the station. In the showroom, consider reflections, reading distance and whether the continue button can be reached. A seated person may see a different part of the screen from the author testing while standing. The observation concerns a particular device and place; it does not establish universal mounting dimensions. If a task cannot be completed independently, arrange an equivalent route to support before treating the station as ready.

The mechanism operating a shared terminal also has its own rules. Microsoft Edge kiosk-mode documentation says that an inactivity reset closes the browser. The timeout parameter alone does not restart it; a separate solution is needed.

At acceptance, therefore, check both the end of the old visit and readiness for a new one. A closed browser on the desktop is not a start screen for the next person. If restoring the station fails, the device should clearly indicate that it is unavailable and direct the user to staff. It should not offer a guest remnants of the previous journey merely to keep displaying something.

The next person is part of the acceptance test

In a private session that expires during editing (in Polish), we usually want to recover our own work. At a shared terminal, another person should not recover it accidentally. For that reason, the final test is not performed solely by the person who made the first request. Someone else must arrive afterwards and try to start their own task.

Prepare recognizable fictional data, for example a test address and a set of two distinctive fabrics. The first person finishes the selection, receives the result and leaves. The second opens the catalogue, uses the back button, checks the contact field and the summary. Record the expected result before the test. A name missing from the welcome screen alone says nothing about the state of the other views.

Add the first person's return to the test. The customer comes back after a few minutes and asks whether they can recover their selection. Staff should know where to find an accepted request and how to distinguish it from an abandoned draft. It should not be opened on the shared screen merely because someone recognizes a fabric colour. Prepare the necessary means of confirmation and a place for the further conversation. Otherwise, a well-functioning reset will be bypassed manually at the first request for help.

Repeat the journey with departure before sending, while the result is uncertain and after downloading a file. In each version, also check what the showroom staff received. Data for an accepted case may remain in the company's process even though it disappeared from the terminal. Interrupting a visit should not accidentally close a request the customer has already successfully submitted.

An offline test introduces another dependency. If a site keeps local changes for later submission (in Polish), ending a visit requires a decision about that material. The next person must not receive someone else's queue, and the previous person should not see a promise to send something that has just been deleted. For some tasks it is better to disable collection when the server cannot be reached and offer staff assistance.

Accept the station again after an employee enters staff mode. The test must return all the way to the next customer's start screen. Check that no other window, completed file or access to the employee panel remains open. The terminal view and the device desktop belong to the same real situation, even if different implementers are responsible for them in the project.

Finally, ask someone outside the project: how do they know they can leave, and where will they find their set later? If they can point to the end button and the appropriate delivery channel, the design gives them a clear boundary. The next customer can then start their own selection while staff can still find the previous person's properly accepted request.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear