Pretty difficult question because due to privacy reasons, it’s not that easy to determine whether the end-user is accessing through the Native app or via the Web version. When I google for a custom JS action to check whether it’s a browser or not, the answers are pretty straight forward:
You can however develop 2 different profiles in Mendix. When you can determine which profile the end-user accesses, you can log that (end-user, profile, timing) and verify the timings with your microflow (end-user, timing).
I hope this helps you.
Adding my bit after some careful research. In this case there is no easy option; we decided to create an object that is associated to System.Session upon triggering of the various user profile roles. Likewise, as long as that session remains valid, the object with the needed client info will be available anywhere. For us this meant just adding logic in a couple of places. Hope this helps the community in future ;-).
I might see an easy solution, that if you call the microflow from a different nanoflow in web as in native, pass from that nanoflow a parameter to the microflow holding for example a string parameter “web” or “native”, Enumeration holding that value. then in your ,microflow you are aware from where the microflow is trigerred.
Hope this helps