Architecture of SAP MDK

[boghyon]

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:

1. Apart from the obvious changes over the years (e.g. brand names such as "SAP Cloud Platform SDK for iOS/Android" → "SAP BTP SDK for iOS/Android") and being able to generate web apps, has anything else changed in terms of MDK's architecture?
2. Where does generating web apps fit to the architecture in the diagram? Is it outside of that "Client Application" box? Is NativeScript involved at all when generating and running the web app client??
3. Which notable libraries or web frameworks are used for the web app use case? I could see that at least the UI5 Web Components are used but not for all HTML elements. Or does the web app client consist of plain HTML+CSS, vanilla JS, and the UI5 web components?

The web app use case is a black box to me.

[thomas_zang · Accepted solution]

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.