Does Tauri Mobile supports OTA update?

[fasidOnGit]

I am about to start develop a Mobile app. and I came across Tauri's mobile support. Not sure how stable is to write mobile apps with Tauri at this point ? My deal-breakers would be

• OTA updates
• Location capabilities
• Camera capabilities
• and some more vital for mobile apps

[FabianLars]

OTA updates

Nope. The mobile apps have the same limitations desktop apps have: They compile the frontend assets into the binary so updating them requires a binary update which requires a full app update. -> As far as i understand it, i'm fairly new to the mobile world.

Location capabilities

Yes

Camera capabilities

Kinda. You have access to kotlin/swift so you can do whatever you want. We also have a camera plugin work in progress here - idk what it's missing.

[AravindPrabhs]

Would it be possible to write your own update layer for the frontend ? i.e. the app will use background tasks to get the new bundle, if any but how would I got about pointing tauri to a new bundle ? I would rather not do any renaming but keep the original bundle where it is in case of a bad update (maybe some cheap metrics/tests to trigger a revision).

I have played around with wry and serving a static website from a file path and then using a custom protocol to communicate with the web view without the new Tauri release (this was over a year ago). I then updated the static website over git and just refreshed the WebView to get the update. So, I think it is possible but obviously Tauri abstracts over a lot !

[AravindPrabhs]

I had a dig into the source code and I think a possible strategy is writing an OtaAssets struct that takes the EmbeddedAssets in prod reverting when required. This can be assigned to the context that is passed to the builder when running the app.

Context assets:

tauri/crates/tauri/src/lib.rs

Line 381 in 0b79af7

pub assets: Box<dyn Assets<R>>,

Assets trait:

tauri/crates/tauri/src/lib.rs

Line 340 in 0b79af7

pub trait Assets<R: Runtime>: Send + Sync + 'static {