I am in a similar boat! Here is what I know so far...
The application_examples provided in that GitHub repo are either .ucf (Unico Configuration File) or .h (C++). The README contains more specifics, but I'll describe the general usage below:
The .ucf files are designed for the Unico/Unicleo/AlgoBuilder GUI tools from ST. If you want to use these files for evaluation, you'll need at least one of those tools, and the supporting development hardware (i.e. ProfiMEMS, X-NUCLEO, SensorTile) to run any examples.
The .h files contain the same info that the .ucf files do, but work with C language compilers for hardware that can run it. For evaluation, I would suggest avoiding this option.
It seems like using MEMS Studio is going to be the best option for designing and evaluating custom FSMs, as their "Advanced Feature" FSM tool feels a bit more intuitive. Refer to UM3233 for more info on MEMS Studio.
MEMS Studio also lets you load-in FSM examples like Unico/Unicleo/AlgoBuilder, however, it requires .json or .fsm file types, so the .ucf and .h examples provided in the GitHub Repo will not work. I do not believe you need to connect supported hardware to build an FSM or load in an example, but you will if you want to run any.
MEMS Studio includes some examples, which you can find in the menu indicated in the screenshot I included.
I have been working on my project for a few days now, and I will say that learning to use FSMs feels like a steep learning curve, but I can tell ST has created a lot of really useful tools to make it accessible.
