A rendering device 115 may also account for circumstances in which they are not powered on, and circumstances where they interact with other devices to create shared experiences (but in which the other devices may have the same capabilities).
The xR registry 130 may retrieve one or more of the xR experiences 140 from an xR warehouse 135 and return the appropriate xR experience 140 for the device. In another implementation the xR registry 130 may return a pointer or reference to an xR experience 140 to the requesting device and then the requesting device can make a subsequent call directly to the xR warehouse 135 to retrieve the xR experience 140.
In one implementation there may be multiple xR warehouses 135 that the xR experience 140 could be retrieved from. The xR warehouses 135 could be separated by user device 110 manufacturer, by advertiser, or be spread across the internet 125 where each xR experience 140 owner can host and deliver the xR experiences 140. The xR warehouse 135 may be stored in many types of storage devices and technologies including a file system, relational database, NOSQL database such as MongoDB, or a blockchain distributed ledger.
In some cases, aspects of an xR experience 140 may depend on the capabilities of the rendering device 115. For example, the rendering device 115 may determine a resolution level of the rendered xR experience 140. In other examples, the level of resolution or rendering quality that that can be applied to the xR experience based on a rule, right, or actor.