Survey questions

[NiklasMerz]

Please add your questions and upvote those you would include in a survey.

[abhijith97]

Adding a few questions that come to my mind in no order:

• What use cases do you use a WebView for?
• What are top 3 WebView features you use as a WebView developer?
• What are top 3 pain points you face as a WebView developer?
• How do you work around some of the shortcomings of WebView today?
• What are your thoughts about WebView from a privacy and security point of view?
• How do you decide when to use a WebView vs navigating to a browser app?
• What specific platforms do you develop on?
• Do you know how to file bugs and search for documentation about WebView?
• Do you feel WebView documentation is adequate?
• How do you keep track of web platform features that are available in WebViews?

[aluhrs13]

What use cases do you use a WebView for?

Probably should include our defined set of usages as examples - Hybrid app, browser, mini apps, and super apps.

What specific platforms do you develop on?

Maybe add "and which WebView do you use on that platform"?

[abhijeetk]

[Compatibility] : How you are achieving consistent behavior and rendering across different platforms and devices using webview ?
[Testing] : What approaches do you take to test webviews and ensure their behavior remains consistent across various devices and platforms?

[abhijeetk]

[interoperability] : What programming language is utilized in your embedding solution? (Embedding a webview in C++, C# etc)

[aluhrs13]

Are there features or functionality missing from Progressive Web Apps (PWAs) that if added would motivate you to maintaining a PWA instead of your WebView-based solution?

[tidoust]

The different dimensions covered by the questions proposed so far look good to me. I note that all of them are currently written as open-ended questions. Whether they should be reformulated with a restricted set of options may depend on the methodology that the group may want to follow, and on the overall resources it may inject into it.

It the survey is run as a bounded series of developer interviews, an open-ended approach seems good... but then running developer interviews is costly! If the is idea to request an a priori unbounded set of developers to take an online survey, then running the survey is cheap but the cost of the analysis and categorization of open-ended responses shouldn't be underestimated. One recent example is the State of HTML survey, for which the publication of final results is still pending because the survey contained a number of free form questions that take time to categorize (and required changes to the survey tool used under the hoods), all the more so as tens of thousands of developers took the survey.

[tidoust]

Hadn't seen that @NiklasMerz already started converting open questions into closed ones in the survey repository.

[NiklasMerz]

Let's continue this in this repo with PRs. Please submit your ideas with questions, answers and possible audiences.

[espinr]

Hi @NiklasMerz , I'm opening some issues directly in the survey repo for a better traceability. After the discussion I can push them if needed.

[NiklasMerz]

Hi @espinr. You can create PRs updating the document directly if you want. You ideas look good to me.