2 ms·
I mean, re: point 1, we're talking about an app that calls an API for every interaction already, so that doesn't seem super relevant. If Claude is down, you can
by entropicdrifter 2y ago
I mean, re: point 1, we're talking about an app that calls an API for every interaction already, so that doesn't seem super relevant. If Claude is down, you can't use it whether it's through a PWA or an Electron app.
- vunderba 2y ago> "Lots of people are correctly suggesting this could function just as equally well as a PWA, but I will point out that (all things being equal) there are SOME VALID USE-CASES" YES - I am speaking GENERALLY. That's why I literally called that out in my comment that this particular use-case (Claude Desktop) could easily be done with a PWA.
- entropicdrifter 2y agoGotcha. Sorry, I guess that was unclear to me based on your phrasing. When you said "some valid use-cases", I thought perhaps you meant (for this app) and not (for Electron apps in general) as the implied next clause.
- vunderba 2y agoNo worries, yeah I just meant that if a dev has no intention of building a native app and is only deciding between either a PWA or an Electron/Tauri App, then there are some advantages to the latter.
- entropicdrifter 2y agoI'd say for the case of Tauri it's doubly so. You can have natively compiled Rust code for especially compute-intensive functions, rather than having it running via WASM.
- lostmsu 2y agoIf you could access chats offline, that'd be useful. But you should be able to do that with PWA.