To those of you who presume that it is a simple matter to port EScribe to Mac - it's not. It is very common for hardware devices to lack Mac support for the simple reason that there are a great number of USB communication chipsets that have no Mac driver. It requires a completely different set of programming skills to write OS drivers - and in order to do so, you must have sufficient documentation of the chipset's low-level interfaces. Chipset manufacturers release SDKs to create drivers for specific applications. Evolve did not design their own USB chipset. They did what all hardware manufacturers do. They used an existing chipset, which provided a Windows SDK to create said driver. Lacking a Mac SDK for said chipset, Evolv is powerless to port their driver to Mac. Furthermore, if their software is written in C++ as is the majority of Windows software (save for the .NET family), this presents a whole new set of challenges. It would require nearly a complete rewrite of the platform, and a different set of programming skills. ObjectiveC and Swift development is quite a different beast than Windows C++. Could they do it? Were the driver problems resolved, something that would require the support of the USB chipset manufacturer, yes, they certainly could eventually. Should they divert their development efforts away from Windows to do this? It is likely an economically foolish decision to do so. I speak as a Mac user, a developer, and the head of a development team.