It is usually preferable to use a nanoflow rather than a microflow. Indeed there is a Mendix Performance Best Practice which covers this “Convert Eligible Microflows to Nanoflows [MXP006]”
This isn’t that easy to do and so it would be good to have an automation to support this
It does also highlight the issue that users need be aware of whether they should be running on client or server and this decision is fixed by choosing to create a nanoflow or microflow.
I think the ideal situation would be that we just have “Flows” for functionality. There could be an attribute which enables us to choose whether they are client or server and this would also affect what is available in the toolbox.
Better still, this could be set to automatic to allow Mendix to decide whether the Flow should be client or server based on what types of activities have been used