[logankeenan]

I’ve been using Tauri for an app I’m developing. The Tauri team is super helpful in their Discord channel. Writing everything in Rust, including the UI (using Axum) has been nice. I’m really excited for 2.0 and mobile support!

My app (very beta) https://meshly.cloud

[jemmyw]

I'm using it for https://mixitone.com originally it was going to be just a web app, but making it work offline was quite compelling. Being able to access NFC card readers with rust code was the clincher.

I wouldn't say the team has been very helpful though. I think I've asked 2 questions on their discord channel. The first the response wasn't unfriendly but they clearly didn't read my message about what I'd already tried and it was along the lines of "just do this as documented here" which was in the message. The second time nobody replied. I self replied with my solutions but no one seemed interested, so it didn't feel like much of a community to start engaging more with.

The testing situation isn't very good. They have an unstable webdriver to try. My existing web code was already covered with playwright tests. I ended up writing a websocket layer to pass all the events and commands to a browser so playwright could drive the browser as if it were a tauri window. I'm happy that I can exercise the whole codebase and share tests between the web app and tauri app, but it's not a great solution. If I were a company making money rather than one person doing a side project I'd love to contribute to the test tooling.

[logankeenan]

> I ended up writing a websocket layer to pass all the events and commands to a browser so playwright could drive the browser as if it were a tauri window.

I was just about to start doing something like this as well for end-to-end testing. Do you have that on Github or be willing to share more about your approach?

[jemmyw]

email me using the address in my profile and I'll send you the code. It's not pretty. I needed to vendor tauri too in order to change the visibility of one function.

[idle_zealot]

Nothing says "private mesh app" like signing up for an account.

[logankeenan]

Thanks for the feedback. I use the accounts to know which device want to be connected. The devices create a mesh network via webrtc. Perhaps, I need to make it more clear why accounts are needed.

[idle_zealot]

Or you could generate device IDs/QR codes for pairing, a la Syncthing.

[logankeenan]

QR codes would be a great addition. I've even tested out sending the WebRTC offer/answer via a QR GIF (due QR image data limits) to make the connection very private. The account solution was quick to setup for now and allowed me to easily test the network conditions with peers across the US (I'm in Iowa). A QR code solution or some other solution that makes it super simple to connect devices is definitely a priority for the future.

[gslepak]

Very cool! Is a Linux version coming?

[logankeenan]

It's not high on my TODO list for the project, but shouldn't be too much work. I'd give it a try if you're interested. Want me to reply to your comment when I get a Linux version released?