It is recommended that you learn about SOA (Service-Oriented Architecture).
Due to historical reasons, many of the ordinary Web have not yet switched to SOA architecture, while Apps are new applications (and because of their Native characteristics), and many of them directly adopt SOA architecture.
If you imagine that the browser and App are both clients (C), and the server (S) both provide interfaces in the form of HTTP API, then there is no difference between the two. If the app is written using a Hybrid framework such as Codorva, then the difference between them is only the difference between the browser framework and the Hybrid framework. This difference has nothing to do with the server.
Theoretically, there is no difference. For example, they all use tcp/ip protocol stack, http(s) and so on. In fact, it is completely possible to make a set of interfaces common to mobile and web pages.
However, the mobile side has more push actions, while the web side has more response actions. Although the web side has a certain MVC layering, in fact, the coupling is generally stronger than that of the app side.
Modify the website’s view layer template engine to a rest that sends and receives json and it becomes the app backend. Generally, the HTTP interface of apps is more rigorously designed than websites; also, apps generally use tokens, while websites use sessions to "maintain state"
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It is recommended that you learn about SOA (Service-Oriented Architecture).
Due to historical reasons, many of the ordinary Web have not yet switched to SOA architecture, while Apps are new applications (and because of their Native characteristics), and many of them directly adopt SOA architecture.
If you imagine that the browser and App are both clients (C), and the server (S) both provide interfaces in the form of HTTP API, then there is no difference between the two. If the app is written using a Hybrid framework such as Codorva, then the difference between them is only the difference between the browser framework and the Hybrid framework. This difference has nothing to do with the server.
Theoretically, there is no difference. For example, they all use tcp/ip protocol stack, http(s) and so on. In fact, it is completely possible to make a set of interfaces common to mobile and web pages.
However, the mobile side has more push actions, while the web side has more response actions. Although the web side has a certain MVC layering, in fact, the coupling is generally stronger than that of the app side.
If the web is separated from the front and back ends, the difference will not be big, but there may be differences in security and sessions.
Modify the website’s view layer template engine to a rest that sends and receives json and it becomes the app backend.
Generally, the HTTP interface of apps is more rigorously designed than websites; also, apps generally use tokens, while websites use sessions to "maintain state"
It’s the same in my eyes.