SAPUI5: What are the strengths and weaknesses of sap.m.Shell and sap.m.App as a container for the application shell?
What are the strengths and weaknesses of sap.m.Shell and sap.m.App as container for SAPUI5 application shell? I am currently using none of them, but I see the benefits. SAP best practice is to use one of these or host them as a wrapper> application. What are the strengths and weaknesses of the approaches?
source to share
sap.m.Shell
: The Shell control can be used as the root of applications, it can contain SplitApp
an App or SplitApp
. The skin provides some overarching functionality for the entire application and provides visual adaptation, such as a border around the application, on desktop browser platforms. Provides an interface for logging out, installing homebackgroud and other things. The app is an aggregation for the shell. Basically allows you to have user level settings and so on
sap.m.App
: The app is the root element of the UI5 mobile app. It inherits from NavContainer
and thus provides its own navigation capabilities. It also adds certain title tags to the HTML page that are considered useful for mobile applications. This acts as a container for your views with navigation functionality.
Best practice: nest them as a wrapper application. So you have a clear separation between applications and under the same shell. Shell provides more options than sap.m.App, although you can reach them in a crude way. In my opinion, their investment is the best solution.
source to share