I. Web App
The concept that corresponds to the Web App is the-Native App local application. In the age of movement, users spend 87% of their time Native Apps and only 13% of the time using Web Apps.
However, the S a big BUT-87% of the time, 80% contributed to the first three Apps, that is, if your Native App is not the user's high frequency of use of the first three words, then basically developed no one to use. So in this case, it's better to make a web app that lets users use it occasionally from time to time.
So there is the concept of PWA.
The role of PWA is to enhance the user experience and meet one-off requirements), the core of which is to make a Web App deliver the same reliable, stable, secure, and interactive user experience as the Native App. Handwriting a logical tree:)
What's interesting here is the caching strategy.
Includes, but is not limited to (slightly advanced, maybe programmers can understand):
Cache, Falling back to network cache priority, failure to access the web;
Networks, Failing back to Cache network priority, failure to read the cache;
Cache then network first reads the cache, and then updates the content from the network; Generic Fallback the general fallback process; (that is, if both fail, reload.)
During the page, a game or something like this will be displayed to help users pass the time)
The Cache and network Race simultaneously reads the network and cached content and accepts the fastest return results among them;
(It turns out that behind every page that can't be read, there's a code farmer who thinks about the caching strategy, so cute)
IV. Https This is not much to say, professionals will understand. The PWA Web APP will enable full station HTTPS for increased security. I know it's Https now, too. Praise one. Authentication, confidentiality, and information integrity can all be guaranteed, especially e-commerce Web Apps that involve payments, which is especially important. This sentence is the speaker's earnest admonition to the farm farmers, hahaha ~