When designing an embedded system with an MCU, one of the hardest tasks for an engineering team is deciding on the type of “brains” their new electronic product really requires. While there are really only two (and some in between) choices to choose from, the decision made can influence (and constrain) future GUI decisions.
It is also essential to consider the implications of the graphical user interface (GUI) development software you choose to use on it. You need to ask your embedded GUI software vendor if the GUI you create with them will scale across their (or others) hardware with ease at a later date. Some software companies, usually the free ones included with the hardware, restrict this to the same processor family.
Mapping out a migration path for potential hardware change is critical to ensuring a longer life for your product, and ensuring you make the right hardware and GUI software decisions. Fortunately, you have options.