6 ms·
Sounds like a webview loading a Next.js application wrapped in a Rust binary targeting iOS? For me, it always felt much more difficult to match the native ui b
by wdb 4y ago
Sounds like a webview loading a Next.js application wrapped in a Rust binary targeting iOS?
For me, it always felt much more difficult to match the native ui behaviours in a web application that it defeats the time won. Especially, when you want to support both Android and iOS.
- DanielHB 4y agothe main advantage vs other webview-wrappers is that technically your native code is crossplatform to Android/Windows/MacOS This is important for a few specific types of applications, for example, my app uses a custom network protocol and it would be nice if I coded it for only one platform while avoiding C++ linker hell in 4 different platforms
- intelVISA 4y agoMight sound wild but network-order bytes are pretty platform agnostic.
- wdb 4y agoNot sure, what you mean, but in a non-webview wrapper application everything but the UI code was already shared between platforms? At least in the apps that I worked on. State machines, fetching logic, app flows etc
- usrusr 4y agoI agree in so far that on mobile, tauri is hardly more than yet another webview based cross platform framework. Perhaps better than others, perhaps worse, who knows. But on desktop, Tauri is a true gamechanger. Enabling apps to build on the system webview instead of shipping a full grown browser with each installation, that's huge. And now Tauri gets "also does mobile, when you need it", this will make it far more attractive. Not only for apps that might have a mobile use case, but also for developers whose skill investment in Tauri becomes a lot more useful if it can also get applied to mobile.