The Big Picture

Not just for the firmware that lives and runs on the device, but the software that people will use to interact with your device, and the design files that will make your electronics part of the real world, too. But we are focusing on the software, first.

The Argument for Qroma

Qroma was developed to simplify this sort of embedded app development. Not just for the firmware that lives and runs on the device, but the software that people will use to interact with your device, too. Think smartphone and PC apps.

In all cases, communication between all of the programs written in service of an embedded device should be as frictionless as possible at the development level. In many cases, a framework that handles the boilerplate to handle the language differences that these platforms run on is a reasonable solutions, especially when you are iterating.

The Qroma platform applies years of experience gained through interacting with all sorts of devices (automated microscopes, smart pumping systems, audiovisual equipment, to name a few) and taps into my frustration at having to (too often) define protocols and handle communication on the device and application ends.

Qroma integrates the communication schema tools and processes I've discovered or invented and couples them with Qroma libraries (to go across different platforms) so that you are writing code that is unique to your application, not commodity communication code that you can imagine has already been written (because it has, here, in these libraries).

It values defining the device interactions and messages and linking them to logic points in languages used by the platforms that will communicate with your device, over protocols/media best suited for the different communication patterns that happen in the life of a device (think installation, configuration, operation).