> The most interesting and difficult constraint is actually software compatibility.
But it is probably the easiest constraint to get around. I would put this one more towards the end of the list.
Not at all. If everything is proprietary you will run into many dead ends. This is totally different than with e.g. standard PC hardware.
There's two big factors that make software compatibility very important for this product specifically.
1. His team is positively tiny compared to what Pebble used to have, and the less software work that's needed, the better.
2. All of the apps and watchfaces people wrote for the original Pebbles were distributed as compiled ARM binaries, so if you picked an MCU with an entirely different instruction set, you'd lose backwards compatibility. ESP32 would fall into that category, for example (not that it would have been a good choice anyway).