wrote:
wrote:
Hi,
In several posts people stated that in a mobile application all screens should be in one eSpace. No one however mentioned the reason for this.
From a maintenance perspective I'd like to split my UI in several eSpaces (like I do in a web application). I've created a sample and it worked. I have a main screen which is the module from the orchestration layer, which calls a screen from another module as an "External Site". As long as the user providers of both screens are the same no problem arises from an authorization perspective.
The application also works fine, when deployed as an apk on an Android device.
Does anyone know the problems which may arise from splitting a mobile application in several UI eSpaces?
Your help/thoughts are apreciated,
Matthieu de Graaf
In a project, before the screens are split, but there is performance penalty, so all are put in one module. I think this is performance issue.
regards
This could be an issue. I noticed a perfomance difference between the 2 solutions (calling screens from another eSpace and calling screens with webblocks from another eSpace).
regards,
Matthieu