Touch instead of a mouse
The interface needs to work naturally with a finger. Touch targets, spacing, and feedback after a press become much more important than on a traditional desktop website.
← Projects
Touch kiosk · Physical UX · Interactive software
How does a web application become software for a physical touch kiosk?
DAVO Technology requires a different way of thinking from a traditional website. The user is standing in front of a physical device, interacting by touch, and expecting every next step to be immediately understandable.
Next.js · Touch UX · Multilingual · Product discovery
Context
The browser is the technology. The kiosk is the experience.
An application can technically run perfectly well in a browser and still be poor kiosk software.
A touch device changes the way users read the screen, interact with controls, and make decisions. A button that feels completely normal with a mouse can be too small or unclear when used with a finger.
DAVO is therefore not simply a responsive website displayed on a large screen. The interface is designed around a specific physical way of using the product.
UX challenges
Every element needs to respond to a different interaction model.
The user is standing at the device
There is little tolerance for complicated navigation. The next step needs to be clear without instructions or a learning curve.
Multiple languages
The kiosk supports SRB, ENG, and RUS, and the selected language needs to follow the user throughout the entire flow.
Different types of users
Some people only want to browse, some sign in, some create an account, and others want product information sent directly to their email.
A complex product range
The system needs to help users move from a large number of products toward the device that is relevant to their situation.
Physical context
The software does not exist in isolation. It needs to work together with the physical kiosk, the screen, and the environment in which the device is used.
First interaction
Users do not have to create an account before they can explore.
The entry screen offers three clear paths: registration, sign in, or browsing products without an account.
Signed-in users can receive product information directly by email, but product discovery does not need to begin with a long form.
Product discovery
The kiosk should help users choose, not just display a catalogue.
Once the product range becomes larger, endless scrolling is not enough. The system needs tools that guide users toward a more relevant choice.
Savings Calculator
A product becomes easier to understand when users can see their own numbers.
The Savings Calculator turns a technical product offer into a much more concrete question: what impact could this product have in the user's own situation?
Kiosk workflow
Behind a few large buttons is a complete user journey.
01
Initial choice: registration, sign in, or browsing without an account
02
Multilingual routing and content in SRB / ENG / RUS
03
Browsing and selecting water-device products
04
Device Finder for guided product selection
05
Device comparison
06
Savings Calculator
07
Advisory flows for home and business solutions
08
Contact and request submission to the DAVO team
Touch feedback
The user needs to feel that the touch was registered.
On a physical device there is no mouse hover state that signals an interaction before the user presses.
Active controls therefore use brief touch feedback to confirm the action without aggressive animation or slowing down the flow.
What this project demonstrates
TOUCH
The same web expertise. A completely different usage context.
DAVO is a good example of why development is not simply a question of choosing a framework. The application needs to understand the device, the physical environment, user behaviour, and the business purpose of the kiosk itself.
The physical context changes UX priorities and affects how even the simplest controls are designed and tested.
Next case study
From a physical kiosk to a data product.
Developer Role Finder solves a completely different problem: how to organize a large volume of developer opportunities so users can find the ones that are actually relevant to them.
Developer Role Finder →