Close integration of client programs and web programs-design conception of AmazeU.net

Due to the limited level of the author, please forgive me if there is anything inappropriate.
There is no doubt that web applications will be a big trend in the future, because the B/S structure has the following advantages over traditional client programs:
1. the B/S structure is browser-based, with rich and vivid expressions, low difficulty and low development cost.
2. Most of the objects in the B/S structure are Internet users and the scope is quite large.
3. the B/S structure system is easy to install and maintain. You do not need to install and install upgrade patches for each user.
However, we also need to see that the web method has inherent defects:
1. slow response speed. even if the information is exactly the same, the user needs to download it from the server every time. The efficiency is much lower than the method that allows the local storage terminal software to "Download once, read repeatedly. Although some client scripts such as jacascript and some new technologies (such as high-speed cache in asp.net) provide some solutions, this problem cannot be fundamentally solved.
2. Poor real-time performance. This is mainly determined by the stateless nature of the HTTP protocol.
3. poor security and confidentiality. because most of the web objects are Internet users, security and confidentiality of information are an important issue on the Internet. Although various technologies are trying to solve these problems, it is undeniable that security is always a relative concept. the inherent deficiency of HTTP brings a considerable security risk.
To sum up, we should combine the advantages of the Client Program and the C/S structure, instead of blindly pursuing new technologies (B/S) or self-sealing, still hold traditional desktop programs. specifically, I have the following ideas (which are also some of the highlights of AmazeU.net ):
1. RSS-based News subscription. In short, each website provides its own content (mainly news, blog, and other content), allowing others to subscribe to it.
For example, I now provide the education news section in our project (AmazeU.net), and then I also provide the RSS service, if someone else uses a client program to subscribe to my news, instead of logging on to the site, if the user subscribes to the RSS service content (blog, if you are interested in other news, you can subscribe to it. In this way, users can easily browse the things they are interested in on each website, instead of logging on to one site at a time.