Adding mobile support to existing v2 project

[reef gazelle]

I would like to add Android & IOS support for the project vibe
I'm wondering it v2 already capable of for this app, basiclly the tauri APIs that it uses is:

Plugins it uses: window-state,fs,(updater, process),dialog, os, shell (for open urls), deep-link (open file from context menu)
Things it does: using embedded ffmpeg (no sub process), whisper.cpp (saves 500mb file), load paths with dialog plugin, get results with tauri events, save with fs plugin.
Things which probably will be useful: actions - does tauri already have actions for IOS / Android? does the updater relevant?
Is PWA relevant here, so somehow I won't need to mess with uploading to app store which requires yearly payment?

Thanks 🙂

[frozen ore]

Plugins it uses: window-state,fs,(updater, process),dialog, os, shell (for open urls), deep-link (open file from context menu)
window-state: irrelevant / unsupported
fs: kinda supported but there are still things unclear
updater: unsupported
process: prob unsupported
dialog: should work
os: should work
shell: only shell.open is supposed to work, but iirc it does not work yet.
deep-link: supported

using embedded ffmpeg (no sub process)
Isn't that against their license? Anyways, something like this will be required because the sidecar feature doesn't work on mobile (and if it would, it'd be android only iirc). On mobile i heard that people use https://github.com/arthenica/ffmpeg-kit but idk how easy it is to integrate into a tauri app.

whisper.cpp (saves 500mb file)
idk probably works

load paths with dialog plugin, get results with tauri events, save with fs plugin.
Should all work, if not it'd be high prio to fix.

Things which probably will be useful: actions - does tauri already have actions for IOS / Android?
Do you have a link showing what you mean with actions? It's such an overloaded term x)

does the updater relevant?
no, that's desktop only

Is PWA relevant here, so somehow I won't need to mess with uploading to app store which requires yearly payment?
No, Tauri is not a PWA thingy. If you want a PWA, you'd have to turn your app into a website (losing access to Tauri's apis).

[reef gazelle]

window-state: irrelevant / unsupported

I understand that probably I'll need to exclude everything that tauri doesn't support on mobile with compile flags

updater: unsupported

I remember that tauri have special config in tauri.conf.json, hope that on mobile it will just be ignored

using embedded ffmpeg (no sub process)
Isn't that against their license?
Yes I think that it's against their license, not sure what to do about. currently on desktop platforms I compile with ffmpeg bindings and add dynamic shared libraries (That's not against the license) in tauri config, in mobile not sure if it's possible currently to add these shared libraries?

Do you have a link showing what you mean with actions? It's such an overloaded term x)
Sorry I meaned Github actions, currently the infastructure is already completly automative for all platforms (commit -> tag -> github action run -> users actually get new version!)
I hope to automate most of the things for mobile too.