undefined

points

[-]

The biggest weakness of a framework like Tauri is the choice to target system webviews instead of bundling a browser runtime.

It seems great to be able to cut hundreds of megabytes out of your app installer, but the platform differences wind up being a complete and ongoing pain in the ass.

Tauri support on Windows is phenomenal.

Tauri on Mac runs into lots of WebKit/Safari issues, especially on older Mac machines that have an older engine that doesn't support modern web APIs. Your app can crash or be left non-functional. You'll find out about these runtime bugs in the wild randomly, and patching for some customers can take days, if not weeks.

Linux support is hellish, and it's best to not even try targeting Linux with Tauri.

Tauri is in the process of adding CEF support. It should probably become the default build target for all platforms.

by jakelazaroff1 hours ago|

parent|

[-]

This point of view always confuses me, because web developers already need to deal with platform differences. Especially if your app app also runs in a browser, like Slack and Discord — at that point, what issues do the differing system webviews cause that you don't need to deal with anyway just targeting browsers?

It's also funny to me as someone who's been building websites for 20+ years at this point, because the platform differences used to be much, much worse. Coincidentally, I just saw this article, which makes the case nicely: https://www.bram.us/2026/06/21/do-websites-need-to-function-...

by c-hendricks9 minutes ago|

parent|

[-]

webkitgtk isn't just quirky, it's also much slower compared to more popular browser engines and is particularly bad with RAM usage.

by synchrone5 hours ago|

parent|

prev|

[-]

Regular Tauri app (aptakube) user on linux here: the experience is very adequate and smooth, I have no complaints. Speed benefits relative to Electron (similar app: K8S Lens) alone are enough to deal with many possible issues.

Could be attributed to app developers going the extra mile, but I suspect it's the framework choice.

by moogly2 hours ago|

parent|

[-]

Targeting and building Tauri apps for Wayland, specifically, is a massive headache due to assorted webkitgtk bundling/incompatibility madness.

by oooyay5 hours ago|

parent|

prev|

[-]

I use Wails which is Tauri but for Go and I don't have the kind of issues you're mentioning. Maybe that is a difference between Wails and Tauri but I don't think the system WebView is a significant factor.

by echelon5 hours ago|

parent|

[-]

Are any of your Mac users using an 10-year old WebView? We frequently ran into that. And there's nothing that can be done about it except engineering around it.

I also doubt it works well on Linux. The performance of webkitgtk is like running an emulator inside an emulator.

by larrysalibra3 hours ago|

parent|

[-]

Can you either at build time or runtime specify a minimum macOS version? No one running macOS 26 (for example) is using a 10 year old WebView.

by jcelerier28 minutes ago|

parent|

[-]

But a lot of people are still running macOS < 10.15

by FooBarWidget3 hours ago|

parent|

prev|

[-]

Web developers already have to deal with different browsers, versions and API coverage.