Live data from Hacker News

Tauri 2.0 Release Candidate

v2.tauri.app

11–20 of 101 posts

Re: Tauri 2.0 Release Candidate

#11
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

There are many things web browser can technically do nowadays, but aren't great or not supported in all browser.

- File System (Obsidian, Logseq)

- Push Notifications (IM, Social Media, Email)

- USB/Bluetooth (Doesn't work in Safari?)

- Global Hotkeys (Raycast)

- Interfacing with other local Apps (localhost is often blocked)

Re: Tauri 2.0 Release Candidate

#12
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

Anything that needs os access, to name some things: menu bar apps, clipboard access, file system, multi window, etc etc.

You can do a lot of things in the browser, but usually it's limited (mainly for security reasons). Having it be an app allows you to better integrate with the OS.

Re: Tauri 2.0 Release Candidate

#13
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

[dead]

[flagged]

Re: Tauri 2.0 Release Candidate

#14
post #3
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

Is it not lighter weight?

Not lighter weight than a website because it is a website. The only advantages are you can ship parts of your app as native code, and you aren't constrained by the browser permission model.

Re: Tauri 2.0 Release Candidate

#17
post #16

Took a look at the homepage ( https://v2.tauri.app/ )... and basically have no idea what this is or why I would use it. Consider adding something more informative than 'Hardened foundation for your web apps', and maybe an 'About' page.

I clicked “Get started…” and saw this:

> What is Tauri?

> Tauri is a framework for building tiny, fast binaries for all major desktop and mobile platforms. Developers can integrate any frontend framework that compiles to HTML, JavaScript, and CSS for building their user experience while leveraging languages such as Rust, Swift, and Kotlin for backend logic when needed.

This ought to be on the front page.

Re: Tauri 2.0 Release Candidate

#18
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

For Slack & co, being able to be on the native application dock (for the average user) instead of buried in a tab is considered a significant visibility boost.

It’s also something that came about from when web apps on desktop/PWA didn’t have nearly as much reach. With e.g modern macOS support for PWAs you might be able to get away with just the web app now, depending on your target customer.

Re: Tauri 2.0 Release Candidate

#19
post #17
post #16

Took a look at the homepage ( https://v2.tauri.app/ )... and basically have no idea what this is or why I would use it. Consider adding something more informative than 'Hardened foundation for your web apps', and maybe an 'About' page.

I clicked “Get started…” and saw this: > What is Tauri? > Tauri is a framework for building tiny, fast binaries for all major desktop and mobile platforms. Developers can integrate any frontend framework that compiles to HTML, JavaScript, and CSS for building their user experience while leveraging languages such as Rust, Swift, and Kotlin for backend logic when needed. This ought to be on the front page.

Yeah for sure. Personally I wouldn't click 'Get started...' on anything unless I already know what I'm getting started with and why.

Re: Tauri 2.0 Release Candidate

#20
post #2

I've been following tauri for a bit. It seems very cool and interesting but I've always wondered - what are the use cases for putting your app in a webview instead of using the browser? Everything I've thought of would work just as well.

Sadly instead of having native apps we have "web" monstrosities... each sporting custom "fancy" UI instead of following the OS native style…
Post reply on HN