The delay and Huawei's support
ISHO's HarmonyOS version is behind schedule. Wang Teng, founder of the company that develops the sleep-monitoring app, publicly stated this in a message reported by IT之家 on November 6. According to the report, Huawei has set up a small working group with its own developers to assist the Oggi Riposa team with the adaptation. This indicates the Chinese giant's involvement, but the material clarifies neither the causes of the delay nor a new deadline.
Current status and announced features
At present, ISHO can be used on Huawei devices through the Zhuoyitong version, a compatibility channel; the native HarmonyOS version, which the company calls 'pure blood,' is still in development. The distinction is significant: availability via Zhuoyitong is not equivalent to an app designed specifically for Huawei's operating system, and it is not known when this transition will be completed.
Asked about integration with Xiaomi's home ecosystem, Wang Teng replied that the company intends to open MCP so that AI systems from different manufacturers can call it. The statement indicates an openness to interoperability, but it does not specify timing, technical methods, or which assistants will actually be compatible. On another front, when asked about the dimensions of the physical product, the founder indicated the possibility of an exchange within seven days without the need to give a reason.
From iOS testing to launch
The app's journey is recent. In September, ISHO began a closed testing phase initially limited to iOS and requiring users to wear an Apple Watch. In late October, Wang Teng announced the official launch, with features including viewing sleep data, an energy score, personalized suggestions, and interaction with ecosystem devices.
The picture that emerges is that of a product distributed across multiple platforms at different times: first Apple, then Huawei via a compatibility channel, while the native HarmonyOS version is still in the works. It is not possible to determine from the material whether the delay is due to technical complexity, limited resources, or corporate priorities, nor whether Huawei's support will translate into an acceleration. It also remains to be verified which features will be available in the native HarmonyOS version and whether the opening to MCP will be accompanied by documentation or a public schedule.
The case shows how a small developer must negotiate access to closed and mutually different ecosystems, with adaptation times that can vary significantly. Huawei's direct involvement suggests that the Chinese company considers attracting applications to its operating system strategic, but without further data it is not possible to measure the effectiveness of this support.
