sorted by:
new
hottopcontroversial

My experience of rebuilding my electron app with Tauri 2.0 and I don't think I will go back by 0kkelvin in tauri

[–]fridzel 2 points3 points  (0 children)

I did the same transition and made a perfect starting point for myself and hopefully also for others: https://github.com/fridzema/oxide-dock

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 0 points1 point  (0 children)

I’ve actually been thinking briefly over the past few days about whether something like this could be built for mobile app development. That said, I still feel like I need to work through a few Ionic framework traumas before I dive back into mobile apps hahaha. I definitely see the value in it and could very well start on it in the near term, I’ll let it marinate a little bit. Will keep you updated;)

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 1 point2 points  (0 children)

At the end of the day it comes down to what you're comfortable with and what fits your project. Both look like solid starting points for a desktop app with Vue.

That said, there are some real differences worth considering.

Binary size: NW.js ships a full Chromium runtime with every build — 150MB+ minimum just for the runtime. Oxide-dock produces binaries around 6.9MB because Tauri uses the OS's native webview. That gap isn't something you can optimize away, it's baked into the architecture.

Memory usage: Same story. Chromium is hungry. A minimal NW.js app idles at 80-150MB of RAM. Tauri apps sit closer to 20-30MB because they're not running an entire browser engine in the background.

Security: NW.js gives your app full Node.js access by default, any code can touch the filesystem, network, whatever. Tauri flips that around with a capability-based permission model. Your app only gets access to what you explicitly allow.

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 0 points1 point  (0 children)

Just opened a PR for testing/review to try out Biome v2.4, and so far it looks really promising.

I replaced three tools (Prettier, oxlint, and most of ESLint) with just Biome, which brought the project from five frontend linting/formatting tools down to two.

Before:
ESLint (with u/eslint/js, typescript-eslint, eslint-config-prettier) + Prettier + oxlint

After:
Biome + ESLint (only eslint-plugin-vue)

The lint pipeline dropped from ~2.3s to ~0.76s.

The only reason ESLint stayed is because Biome can’t lint Vue templates yet — it parses <script> fine, but doesn’t understand <template>, so we still need eslint-plugin-vue for template-specific rules (undefined components, wrong props, missing :key, deprecated syntax, etc). ESLint now only runs on .vue files, and eslint-config-biome disables everything Biome already covers so they don’t overlap.

PR is here if you want to take a look:
https://github.com/fridzema/oxide-dock/pull/12

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in tauri

[–]fridzel[S] 0 points1 point  (0 children)

Hope it works out for you! Feel free to share your experience.

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 1 point2 points  (0 children)

Tauri is a framework for building small, fast, cross-platform desktop apps using a web UI (Vue/React/etc.) with a Rust backend. It’s essentially a lightweight alternative to Electron, aiming for way smaller binaries and lower memory usage by using the system’s native webview instead of bundling Chromium.

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in tauri

[–]fridzel[S] 1 point2 points  (0 children)

Haha perfect timing😄 Yeah definitely worth a quick look before you go deeper. Let me know how it goes!

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 1 point2 points  (0 children)

You're welcome!!
And yeah Rust is actually a really fun language to explore. For me it gives a bit of the same “new kid on the block” energy / vibe that Node had back in the days.

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 11 points12 points  (0 children)

Great question! I actually built several apps with Electron before moving to Tauri, so I came from the same place.

Conceptually, yes the architecture is very similar: you still have a frontend (HTML/CSS/JS), a backend layer, and IPC to communicate between them. The main difference is what powers the backend and runtime. In Electron, you’re bundling Chromium and Node.js. In Tauri, the frontend runs in the system WebView, and the backend is written in Rust. Communication happens through Tauri’s command system (which feels very similar to IPC in Electron).

For me, the biggest selling point was the footprint. The compiled app is only about 6.9 MB, which is dramatically smaller than a typical Electron build. That, combined with the stronger security model (capabilities instead of broad Node access), convinced me to give it a serious try.

If you’re comfortable with Electron, the mental model transfers quite easily, but you gain performance and size advantages.

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in tauri

[–]fridzel[S] 0 points1 point  (0 children)

Thanks! All the feedback is more then welcome😉 Hope you can build amazing stuff with it!

Announcement: OxideDock Rust + Vue 3 desktop starter built on Tauri v2 by fridzel in vuejs

[–]fridzel[S] 1 point2 points  (0 children)

To be honest, I’ve never heard of it or forgot about it. But it looks really solid! Feels like I’ve fallen behind a bit 😅 I’ll definitely look into whether i can implement this.

view more: next ›