I've wanted to play around with a color ePaper watch for a while, including debating buying an old Pebble Time, so this seems like a great excuse to pull the trigger.
For people who have developed apps for them in the past, does everyone just use the embedded JavaScript engine? For maintaining apps that modify the firmware or talk to new peripherals does that require maintaining a fork or is there some module system?
Get on their discord. Bangle has the JS thing, pebble watch faces used a c-variant, I don't remember if their applets used something different.
AFAIK, if you're doing firmware replacements you're likely going to be maintaining an "out of tree fork" unless it's already well-modularized in the way you're imagining.
For people who have developed apps for them in the past, does everyone just use the embedded JavaScript engine? For maintaining apps that modify the firmware or talk to new peripherals does that require maintaining a fork or is there some module system?