The session will look at how the Oniro stack was built starting from a business problem definition and moving through further integration of de facto standards, widely used technologies, and compliance processes/test suites. The audience will be exposed to the thought process of prioritizing and focusing on minimum viable early deliveries with incrementally more complex functionalities and use cases. The audience will learn the standards analyzed and selected by the Oniro project to be compliant with in order to enable maximum interoperability among devices and smooth the migration from similar alternatives. Some of these standards: bitbake and yocto project, linux and zephyr, musl and GCC, openchain, project matter, openharmony,...
The audience will also become familiar with areas that require standardization yet have not been standardized yet such as system update, semantic web and autonomous cooperative devices, device management, user registration and data handling, and device onboarding processes and data structure.
No prior knowledge is required. Hopefully, attendees will bring home some lessons about avoiding NIH syndrome in order to gain maximum market viability while focusing efforts in those areas that can lead to innovation.
