As much as I want to answer by focusing on the "why", as splitting it doesn't always make sense, I'll stick to the question at hand assuming there is some need for the components of the app to be leveraged by other apps (such as messaging).
But circling back to the larger issue, make sure you have a compelling reason to split an app up. If organization is the issue, do it with modules first regardless. Separate apps incur license costs and overhead that might not be needed.
The approach I see mostly (and I have worked with multi app Mendix solutions a lot):
Hope this helps!
Hi Ralph,
Facing the same issue in other app. What the worries are:
Short update on our choice:
With Danny Roest from Mendix expert services we concluded that for high performing front end user experiance a solution with iframes or switching between apps wil not be enough. Therefore we are going for an architechture in which we have one single Front end application.
During the development of this application we wil make continue using the modules of Mendix to have any 'complex' logic for data enriching seperate from the viewing objects and screens. This wil make it possible for us to split this logic into a seperate application once this is needed from a performance or complexity point of view.