search

WebView-CG / usage-and-challenges

Documenting usage scenarios for WebView and the challenges they create
https://webview-cg.github.io/usage-and-challenges/
Other
12 stars 4 forks source link

Add dfns and rewrite concepts slightly #45

Closed tidoust closed 1 year ago

tidoust commented 1 year ago

This editorial pass aims at improving the overall readability of the document, reformulating some of the concepts to reduce ambiguities and leveraging ReSpec's ability to reference definitions.

Scenarios appendix left untouched for now. I'm happy to continue with these updates if they look useful.

I note that the implementations table still contains "Tie WebView and native APIs together" and I do not understand what that means, so don't know how to reformulate. Could someone clarify the intent?

rayankans commented 1 year ago

I note that the implementations table still contains "Tie WebView and native APIs together" and I do not understand what that means, so don't know how to reformulate. Could someone clarify the intent?

I believe the intent is that the WebView can provide OS-level features to the web-content. @NiklasMerz is that accurate?

NiklasMerz commented 1 year ago

Yes that's what I tried to say. WebViews can make OS features available for web content. Apache Cordova or Capacitor for example have plugins that provide JavaScript APIs in their WebViews that allow developers of web content to interact with native OS features that are otherwise not available in "normal" web browsers.

tidoust commented 1 year ago

OK, then I made another attempt to clarify what "access to the web content" entails, and to reference that directly from the table.

I also took the liberty to add more generic definitions of "native applications" and "web applications" to better set the context under which WebViews are used. All of these definitions can probably be further improved :)