From ADRC Guide 2.3 ADRC key concepts ADRC is based on some key...

From ADRC Guide


2.3 ADRC key concepts
ADRC is based on some key concepts that provide both simplicity for users and fexibility for product
developers. These concepts are:
• The user only needs one app to on-board, control and monitor all their Things and this is the device browser app (DeB)
> Just as there are multiple web browsers for a user to choose from, it is envisaged that in the future there will be multiple device browser apps from different suppliers and the user will be able to
choose their preferred DeB app
• A licensing model whereby only the IoT stack embedded in a Thing’s microchip is licensed and the rest of the ADRC solution is open source. The open source components are the:
> Device browser app (DeB)
> Resource Modelling Language (RML) that is used to describe a Thing and its functionality
> Resource Control Protocol (RCP) that is the protocol used to transfer RML fles and commands
between the Thing, the IoTG and DeB
> ADRC server software for an Internet of Things Gateway (IoTG)
- Just as there are multiple Wi-Fi modems for a user to choose from, the IoTG will be provided by
multiple suppliers


IMO, If Telink's chip is in Apple Homekit products, as confirmed .... ie with ADRC ... and Apple Homekit hub is to be made connected with all products with ADRC, then the above applies. The apps is the open source app from ADRC (as highlighted above).

Right now, I don't see any other competitor to ADRC in the market. Do you?


PDYOR