According to lisa.haag's blog post, the architecture of SAP MDK looked like this in 2017:
(SEAM is the former name of SAP MDK)
That blog post is very valuable to my research since it's the only public resource so far that gives a short insight of how MDK is actually architectured. Unfortunately, it's a bit outdated. While the fundamental idea to leverage NativeScript didn't change, several new features have been added to the architecture - most notably the incorporation of generating web apps.
Hence my questions:
The web app use case is a black box to me.
1, The architecture of MDK mobile app client depicted in the diagram is not changed.
2. NativeScript is not involved in MDK web app client, which implements similar functionalities of mobile SDK and NativeScript modules in its own, and it is deployed to CF on BTP.
3. MDK web app client consists of plain HTML+CSS, React JS, and UI5 web components.