yeah I’ve gotten android to work but its been a journey. still feels a little underdocumented and bleeding edge, but then again got it working finally. look to the examples and not the docs IMO
If you only will use what’s in the standard tauri js api, or in the standard plugins, then technically you don’t need rust. But yeah I think if you wrote a bunch of apps in it you’d inevitably want to make your own plugins or backend code, and then you’d need rust.
Depends. I made one in tauri and it was a good fit because I already had a web frontend and rust backend. I was able to reuse both of those with minor changes, now the same code builds the app and the web server/frontend.
I’d probably go native if:
you’re only developing for android and don’t care about desktop/ios/etc…
UI performance is really important, like for a game
You want to minimize app size
You aren’t skilled at web front end development
With tauri, if you need phone apis that aren’t in the toolkit already you’re going to jump through some hoops going from javascript to rust to kotlin and back again. Its a significant barrier, you’re handling serialization/deserialization of function arguments/results in 3 different languages.
So, what is the security surprise? “When writing an email in the Gmail app on your Android device, you can now drag and drop contacts in the addressee fields,” Google said.
Ah, the “play store”. Happy playground of spending! Starting off on the wrong foot with just the name. Of course its a trashed up ad spew bucket and dark pattern shitehole.
yeah I’ve gotten android to work but its been a journey. still feels a little underdocumented and bleeding edge, but then again got it working finally. look to the examples and not the docs IMO