However, both can have a bug that exposes XSS and give direct access to all the nice APIs both add.
For example, adding a SQLite plugin gives the attacker full access to all local db data for the app. Or node APIs vs FileSystem APIs.
The solution to have have two threads and let the dev specify their own API to communicate.
Electron had bad solutions for a while but it’s gotten better these days and might offer some ideas
I’m a fan of your work improving the stalled Apache product and moving it forward as Capacitor. I use it! v2 though, as I haven’t upgraded to v3. Maybe I’ll try that this weekend.
eg my app needs to access a bluetooth module or uses opencv: would it be easy to plug in an existing Swift/Java libraries that has deps on these low-level stuff (without mingling too much with the build process like enabling or turning off some flags, hijacking some of Capacitor's own build processes, etc)
What advantages do you think Capacitor has over React Native?
Ultimately Capacitor is the most true to web development of the alternatives out there, so if that matters to you it’ll be better on that front.
It’s also a lot simpler than RN and feedback has been there’s a lot less upgrade hell with Capacitor
If you aren't familiar with Capacitor, it's a way for web devs to build cross-platform apps using standard web technology and any popular web stack. For example, you can build mobile apps using popular stacks like Next.js + Tailwind as in this example: https://github.com/mlynch/nextjs-tailwind-ionic-capacitor-st....
We've got some exciting things in the pipeline like a Project API for automating configuration (whitelabling/CI/etc), E2E testing, easier native HTTP features, resource generation (splash/icon/etc).
Happy to answer any questions about Capacitor!