Apache Cordova VS awesome-tauri

Anyone have experience with/opinions on Apache Cordova? [1]

It seems like it would solve most of the PWA issues. Although I vaguely recall reading that Apple is not too fond of apps that are basically just wrapped web views.

[1] https://cordova.apache.org/

Has anyone tried pwa builder?[2]

Thank you for any insights!

[0]https://cordova.apache.org/

A little over a decade ago, I worked on the open-source project Apache Cordova/Adobe PhoneGap, first at IBM and later at Adobe. Apache Cordova enables you to build mobile applications using HTML, CSS and JavaScript while targeting multiple platforms with one code base. In today’s technology landscape, mobile is dominated by iOS and Android. In the early 2010’s we were awash in mobile platforms from BlackBerry, Microsoft, Firefox, Tizen, etc. Targeting multiple platforms, including the web, from one codebase was a game changer for overworked development teams.

There are layers that offer access to native APIs like capacitor, cordova and nativescript. Apparently sometimes multiple of them should be used, but I didn't understand what are the differences even after reading the announcement. These seem to be frontend agnostic technologies and Capacitor is apparently the more modern choice at the moment.

To be honest, we have not only Capacitor but also Cordova which Capacitor is based on but because Capacitor is more popular, has better community, deals with some problems better, and works beautifully with Ionic Framework I will tell more in a second, I simply recommend Capacitor.

Apache Cordova is an example of this. It is also useful if you need to access native code (the camera, database, etc), or to use just as a WebView Container as an application to deploy to the Play store/ App Store

I've had a lot of success with Vue + Cordova. https://cordova.apache.org/

Ratchet, Ionic, Cordova.

I find it fresh and positive that Tauri developers take security very seriously. Before this 1.0 release they ordered a full security audit for the codebase and published the report ( https://github.com/tauri-apps/tauri/blob/next/audits/Radical... ).

The project encouraged me to better my own workflows too, as even the awesome-tauri repo requires signed commits in the PR template :) ( https://github.com/tauri-apps/awesome-tauri/blob/dev/.github... )

Tauri if you are already with Rust.

Here are some open source app built with Tauri

https://github.com/tauri-apps/awesome-tauri

I don't at all expect users to do full code inspections, expecting that would frankly be naive in my opinion for small projects like these. I was just trying to alleviate, not resolve, security concerns. What I am trying to encourage is peer review rather than user review of the code. That's a big reason why I have submitted it to developer resource lists such as Awesome Tauri, to get public peer review.