Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tauri Mobile Alpha Release

tauri.app

Post reply on HN
Print view View original

51–60 of 82 posts

Re: Tauri Mobile Alpha Release

#51

Post by rpastuszak »

sergix wrote: post #17

The Tuauri team needs to focus on maturing its primary codebase and documentation before branching out to assign teams to separate projects like this. I've written a few hundred lines of code using Tauri, and I've had to do much more API wrangling and searching the official Discord than I would have liked -- a lot of valuable API details are tucked away in very specific places, especially related to using Tauri's sta…

+10000 I really enjoyed working with Tauri, but had to drop it because after a few days of porting my app to it, I released that it doesn't support AppStore distribution (i.e. creating properly signed .pkg files). This wasn't clear in the docs, and the videos I watched implied the opposite.

The team is doing amazing work and I don't blame them for this, it's perfectly normal for things to slip.

I'm excited about Tauri partially because (in my specific use case) even if I build for Mac only, the UX I can deliver with it will be much better with a hybrid app than SwiftUI [1].

The lesson here is that if you're planning to work with Tauri and Mac, you might want to focus on testing the entire pipeline (design, develop, distribute) first, and then, once you can push to TestFlight, pushing and testing features. Again, YMMV.

[1] Weirdly enough, there's almost no way for me to build a native app that will beat the performance of an optimised web app. Again, my use case is very specific (a niche text editor), but I find it hilarious given how much sh*t web apps get on HN.

Re: Tauri Mobile Alpha Release

#52

Post by revskill »

johnny22 wrote: post #43
revskill wrote: post #41

Earlier quoted context omitted.

The issue with capacitor and ionic is in legacy, outdated Cordova dependencies !

which ones do they still have now? I know a lot of folks still use third party cordova deps, but i didn't think capacitor did.

For example, i used the http client, but its Android version is just legacy, outdated :(. Not sure if it works with latest Android OS version.

Re: Tauri Mobile Alpha Release

#53

Post by password4321 »

bobajeff wrote: post #16

I've yet to see a Web UI toolkit/framework that works on all of the desktop (Windows, *Linux* and OSX) and Android and iOS. If they manage to pull this off then bravo to them.

Fyne.io supports many use cases on these platforms (+web?) with Go. It would be interesting to build a web UI toolkit on top of it, but I think they've chosen not to.

Re: Tauri Mobile Alpha Release

#54

Post by marcosdumay »

rpastuszak wrote: post #51
sergix wrote: post #17

The Tuauri team needs to focus on maturing its primary codebase and documentation before branching out to assign teams to separate projects like this. I've written a few hundred lines of code using Tauri, and I've had to do much more API wrangling and searching the official Discord than I would have liked -- a lot of valuable API details are tucked away in very specific places, especially related to using Tauri's sta…

+10000 I really enjoyed working with Tauri, but had to drop it because after a few days of porting my app to it, I released that it doesn't support AppStore distribution (i.e. creating properly signed .pkg files). This wasn't clear in the docs, and the videos I watched implied the opposite. The team is doing amazing work and I don't blame them for this, it's perfectly normal for things to slip. I'm excited about Taur…

> it doesn't support AppStore distribution

Ironically, having a team specialize on mobile is a great way to catch this kind of problem.

Re: Tauri Mobile Alpha Release

#55

Post by MuffinFlavored »

MengerSponge wrote: post #24

I watch F1 and just learned about this lovely project, so it's surprisingly hard to parse "Tauri Mobile Alpha"... those words are in the wrong order!

> Scuderia AlphaTauri

https://en.wikipedia.org/wiki/Scuderia_AlphaTauri

was scratching my head for a second, finally got it :)

Re: Tauri Mobile Alpha Release

#56

Post by rpastuszak »

marcosdumay wrote: post #54
rpastuszak wrote: post #51

Earlier quoted context omitted.

+10000 I really enjoyed working with Tauri, but had to drop it because after a few days of porting my app to it, I released that it doesn't support AppStore distribution (i.e. creating properly signed .pkg files). This wasn't clear in the docs, and the videos I watched implied the opposite. The team is doing amazing work and I don't blame them for this, it's perfectly normal for things to slip. I'm excited about Taur…

> it doesn't support AppStore distribution Ironically, having a team specialize on mobile is a great way to catch this kind of problem.

Yes and no, publishing to the Mac AppStore is a slightly different beast.

https://github.com/tauri-apps/tauri/issues/4415

TBF I wouldn't bother with the Mac AppStore if there was a simple way of distributing paid versions of the desktop app without much coding involved.

Re: Tauri Mobile Alpha Release

#57

Post by sergix »

sergix wrote: post #17

The Tuauri team needs to focus on maturing its primary codebase and documentation before branching out to assign teams to separate projects like this. I've written a few hundred lines of code using Tauri, and I've had to do much more API wrangling and searching the official Discord than I would have liked -- a lot of valuable API details are tucked away in very specific places, especially related to using Tauri's sta…

For any specific details that anyone may be curious about, I have a public Notion page with some different documentation issues and the links to their respective sources. [1]

1: https://sergixdev.notion.site/Tauri-Documentation-b695823f0b...

Re: Tauri Mobile Alpha Release

#58

Post by hu3 »

bobajeff wrote: post #16

I've yet to see a Web UI toolkit/framework that works on all of the desktop (Windows, *Linux* and OSX) and Android and iOS. If they manage to pull this off then bravo to them.

Perhaps take a look at https://quasar.dev/introduction-to-quasar#what-is-quasar

You can do all this in a single code base:

- SPAs (Single Page App)

- SSR (Server-side Rendered App) (+ optional PWA client takeover)

- PWAs (Progressive Web App)

- BEX (Browser Extension)

- Mobile Apps (Android, iOS, …) through Cordova or Capacitor

- Multi-platform Desktop Apps (using Electron)

Re: Tauri Mobile Alpha Release

#59

Post by return_to_monke »

solarkraft wrote: post #19

This is a huge reason to go with Tauri over Electron. I don't get why there isn't (or is there) a simple way to package a web app for all platforms. Everyone still makes this weird artificial distinction between Desktop and Mobile despite the technical capabilities and user expectations being close to the same.

https://flutter.dev has very good DX in my opinion for all platforms.

Re: Tauri Mobile Alpha Release

#60

Post by mccorrinall »

dceddia wrote: post #46

I’ve enjoyed working with Tauri a lot, and I’m excited to check out the mobile release. I’ve been using it for about a year now, paired with Svelte, to build a video editor [0] and it’s been really nice speed-wise. I haven’t felt like Tauri is the bottleneck in probably 99% of cases (usually it ends up being my own code!). One area they could improve, and I think they’re working on for 2.0, is the IPC mechanism betwe…

What I’ve been missing in tauri is being able to manipulate the window title bar similar to firefox or vscode (electron actually allows this).

Anyway, regarding your IPC bottleneck: I found it faster to spawn a local websocket server in rust and let my vue app connect to it. It’s really ugly and I hate myself for working like this, but albeit the tcp overhead it is actually faster for transferring bigger amounts of data than IPC.

Post reply on HN