You ask your glasses to start a focus session. A spoken confirmation helps, but you still want to know whether the timer is running and how much time is left. A few minutes later, the information you need has changed.
This is the kind of interaction problem that Rokid AIUI addresses. Short for Artificial Intelligence User Interface, AIUI gives developers a framework for building experiences around AI capabilities. Rokid's AIUI project overview describes it as an agentic runtime for AI glasses with displays. For the person wearing those glasses, the question is simpler: what happens after you ask for something?
The request is only the beginning
The AIUI concepts guide starts with intent: the goal behind a person's request. An interface built around that goal needs to help them follow the task as it develops. Sometimes they need to make a choice or clarify what they meant.
Consider the focus timer again. At the start, you need confirmation that the session has begun. Later, you might want to check the remaining time. The timer is an illustration of the design problem here; it doesn't describe an exact voice command or the behavior of a particular release.
A correct answer can still leave you wondering whether anything happened. Good interaction design has to account for that uncertainty.
Connecting the request to the interface
The AIUI architecture separates an agent's definition, its interface, its runtime logic and the capabilities it can call. These describe the agent's role, what you can see or act on, how the task progresses, and which services or device functions it can use.
A language model may help interpret your request. The application still needs to keep track of the task and show you the result. A device function also needs controls and feedback that make sense to the person using it.
AIUI brings those responsibilities into a shared framework. The developer's implementation and the capabilities available in its environment determine what a particular agent can actually do.
Feedback has to work on glasses
The AIUI interaction guidance covers voice, temple input and head tracking. It asks developers to give clear visual or audible feedback and place important interactive elements within a comfortable viewing area. These are design requirements, so they shouldn't be read as measured guarantees of comfort or reliability.
The display imposes its own limits. AIUI's current Monochrome-green design specification uses text and shapes, with different line treatments, to distinguish states. Color alone can't carry the meaning. Information also has to stay readable against a changing real-world background.
For the wearer, those details affect a basic question: can you recognize what's happening? A pending task needs to look or sound different from a completed one. An attractive overlay can leave that question unanswered.
Where Agent Store fits
The Rokid Agent Store page lists Pomodoro for focus sessions and Word Catch for vocabulary practice. These examples show a catalog organized around activities people return to.
The catalog and AIUI explain different parts of the experience. AIUI describes a framework developers can use; Agent Store presents experiences to users. A framework example alone doesn't establish that an agent is available, and a catalog entry doesn't explain every detail of how it was built.
The current Agent Store page applies to Rokid Glasses. Availability can vary with software and other conditions, so the requirements for the task you want still matter.
An interface on your glasses can use the cloud
The AIUI Cloud overview describes a connection between external systems, Rokid services and glasses. Its stated current capability includes delivering notifications. Selecting a notification can open a registered AIUI page.
That gives a concrete reason to separate where you see an interaction from where its processing happens. Something can appear in your glasses while relying on a remote service.
The existence of an AIUI runtime doesn't establish that every part of a feature runs locally. It doesn't settle data-retention questions either. Those answers belong in the information for the specific service involved.
Check what your device can actually use
AIUI's developer material explains how an experience can be built. Product support information tells you what a particular device and software version can use. The framework's display-based design shouldn't be taken as a promise that every feature works on every pair of Rokid glasses.
When you watch a demonstration, look beyond the initial answer. If a task is waiting for external data, can you tell? When it finishes, is that clear from what the glasses show or say? Those moments tell you how much of the interaction you can follow.
0 Kommentare