Cross-platform Mycroft

[NeonDaniel]

@Steve_Chretien

Regarding skill compatibility, have Ovos and Neon maintained the same compatibility? Personally, I believe everyone should work together to maintain a minimum level of compatibility.

I agree and the intent is to continue supporting the same skills/plugins in Neon and OVOS. Mainly, the Neon services add support and backwards-compat with our server implementations (i.e. https://iris.neonaiservices.com)

@Steve_Chretien

Also, if possible, skills should be created 100% in Python to ensure cross-platform support. Dependencies in C can be a barrier for certain CPU architectures and operating systems.

I believe in practice this is true with the only exception being the Pandora skill from Mycroft days, though I can’t say for sure. Based on the installation/skill management tools we have and are working on, skills should generally be pure Python, but it is worth considering that not all Python packages are cross-platform.

@Steve_Chretien

Another aspect of Mycroft I have considered is implementing communication functions between devices, whether between Mycroft devices of all versions or between PCs (Windows, Linux, and macOS, even though the latter is technically not a PC).

My take on this is that it would be simpler to have a single central instance of the voice assistant (in my case Neon) and a bunch of client devices that connect and offload processing to the one central “Hub”. I’ve started on this in the neon-nodes project; I have some demos in this forum thread.

@Steve_Chretien

Finally, is anyone working on a native Android version?

I don’t believe so. There have been Android projects, but mostly they are client apps that connect back to a core instance running on some other system.