If we decide to use the PIC32MZ for the "Governator", we might be better off to extend an existing simulator to cover the hardware (LCD, Button) and avoid duplicating the code.

Another option would be to use a (very simple) GUI library which works on both, the PIC and some kind of WEB interface.

If we can find ways how to avoid duplicating the code I am all for it.

I saw the online simulator as a simple helper to actually find/share/collaborate on a menu structure that is intuitive with minimal work effort (some javascript maybe).

If you want to run java(script) on the Governator, then you need to plan for more CPU resources, more power, etc.
Doable but not sure it is worth the efford. I.e. it might be simpler/better to use an existing embedded system with
LCD for this (e.g. a Raspberry PI or similar)

I don't want to run java(script) on the governator.

Other side of the problem :

• what resolution do you plan? Color screen or not?
• what kind of ui? Text based on simple lcd or more graphical?

Think of it as the difference between the simple lcd you see on the top of higher end dslr and the live viewfinder at the back.

This for example :

VS

Color LCD with resolution in the 320x240 pixel range around 2-3" diameter. Touchscreen optional (maybe enabled later on)

The initial framework is done: http://files.apertus.org/controller-simulator/

Its only working partially so far but the basic foundation is there now.