We are using the codename at several layers as much as they are all built around the same hardware platform:
- hardware platform identifier
- computer system identifier
- platform for hardware remote development identifier
- wearable personal computer device identifier.
The image of expandable system map above illustrates correlation between those mentioned components:
- for every component there are key features our user needs map defines,
- descriptions of non-common features are given here
- software platform is still to be named, , but we use a codename ArvoOS
- hardware and software platforms are forming a computer system,
- the system, being itself a platform, allows us to develop products: hardware appliances and XR applications that are going to fulfill ARVO mission towards consumer experiences.
Design
As much as progressing with user needs understanding, we are developing also the industrial design approaches for the device:
Entry point audiences and pains:
Additive manufacturing and generative design
End-to-end DLT architecture of the system and environment aforethought to give a rise to full-scale additive manufacturing cycle of the device. While walking the talk, we want to enable users with cosmetic extension components to be generative based on their usage data.
Hardware and software platforms
Both platforms are for the community development as
- Software Development Kit and
- hardware Reference Design Kit.
ARVO leads and moderates, provides tools and components, testing devices access for the community.
Whitebelt
Customizability means users start with basic XR features which we enframe in Whitebelt device (Frame, undividable hardware base).
Whitebelt is expandable up to the Blackbelt with extension components, those we name Belt.
Composition
Our basic composition for the device (please, pay attention the device on the picture is for illustration only) is based on the user needs map feature set