[Front-end knowledge related -JS] understanding of the mobile terminal and Hybrid development?

What 1.hybrid is why the use of hybrid it?

1. concept:
   • Hybrid and mixed-use development is the front-end client
   • Need front-end developers and client developers to accomplish
   • Some links may also be related to the server end
   • Large front-end: Web, APP, front-end and server-side interaction process
2. Existence value:
   • Fast iterative update [key] without APP audit (hybrid technology could one day on the line several times)
   • Experience smooth (and Native development experience substantially similar)
   • Reduce development costs and communication, two-terminal common set of code
     
3. webview：
   • APP is a divalent group of (App can Webview, it may have)
   • H5 is mainly used to load the page, is a small browser kernel
4. file: // protocol
   • file protocol: local files, fast
   • http (s): network load, slow
   • The expansion of knowledge: Web standards are what it?

2.hybrid specific implementation process?

2.1 usage scenarios

1. Not all scenarios are suitable for use hybrid
2. Use NA: the ultimate experience requirements, changes are not frequent (such as headlines Home)
3. Using hybrid: a high experience requirements, frequent changes (such as news headlines details page)
4. Use H5: No experience, not commonly used (such as reporting and feedback page)

2.2 realization

1. Good front-end static pages (HTML, CSS, JS), the documents to the client
2. The client front end to get the static pages, stored as files in the APP
3. Client in a Webview
4. Using the file protocol to load the local static files

3. introduce hybrid and update process on the line?

3.1 advantage

1. A better user experience, experience is consistent with NA
2. Fast iterations without app review [key]

3.2 Disadvantages:

1. High development costs: FBI, test, check the bug are more trouble
2. High operation and maintenance costs. (Platform Maintenance)

3.3 application scenarios:

1. hybrid: a stable product functionality, high user experience, frequent iterations
2. H5: word operating activities (such as red XX), or unusual features

4. How JS front-end and client communication?

1. JSONP manner similar data request
2. Introduction and use of schema Agreement
3. The basic form of communication: the ability to call, passing the callback parameter monitor
4. Understanding and use of schema Agreement
5. Calling code package schema
6. The benefits of the built-in on-line: faster, safer