We've been using Iced for Totem [0], our cross-platform collaborative workspace app. Incidentally we took a similar route to what Discord is aiming to do, layering a rust engine with native UI (e.g. Swift on mobile) and it has been going well so far.
The one major concern I have with this framework, and with rust UI frameworks in general, is accessibility. That's something you get for free or nearly-free in other ecosystems but seems to require a fair bit of elbow grease here.
Still, I would wholeheartedly recommend Iced, with the one caveat that it hasn't yet hit 1.0 and version upgrades could be a little painful, and might bring big changes.
I'm working on Totem [0], feel free to give it a try! I try to post about it in the "What are you working on" thread monthly but haven't mustered the courage to do a "launch" yet.
It's cross-platform, Rust core with native UIs (Rust UI for Desktop, I'm using Iced [1]). I built it due to similar problems, and because I got tired of waiting on nvUltra [2].
Totem is meant to be more of a team/collaboration app in truth, but it turns out that realtime sync is also immensely helpful when working by yourself on multiple devices.
Everything is stored in SQLite and Markdown as well, but in a bit of an obscure location in a thin wrapper format (I might build in an escape hatch later on). The reason to do it this way is largely because allowing people to externally edit Markdown in a live sync context is tricky and I didn't want to make it super easy to screw yourself over.
P.S.: With consideration to the time that I am posting this...the iOS/iPadOS offering is currently restricted to a few countries. If you're not in those countries and are interested, let me know and I can add you to Testflight, or you can use the web version.
Totem is a collaborative workspace, featuring tasks, notes, and docs, built in Rust and available across desktop, web, and mobile (iOS to start) with seamless syncing and offline merge.
I built this because I think there's a lack of true realtime (CRDT) synced notes that aren't built on a heavy platform that take up 1GB+ RAM (Totem takes up ~100MB, and is also generally more responsive due to the local-first + ops-log approach).
Another thing I care about is keeping the underlying data portable: Totem is built on Markdown and SQLite as its core formats, so you get the convenience of cloud-based syncing without locking your data into a proprietary format.
I’m still looking for beta users/design partners before the initial launch. You can try it without creating an account here:
This is a bit of an unplanned post, so the sandbox template is a bit barebones (empty docs, doesn't feature a properly setup table). Nevertheless, I would love to hear your feedback if you try it out, especially if you use collaborative notes/docs today and have opinions on what they’re missing!
I'm continuing to work on Totem [0], an offline-first, local-first, team all-in-one workspace that features live collaboration, databases, and agentic workflows. The desktop apps are built completely in Rust (without Tauri or Electron) and are functional (with a few early users trying them out), while the iOS app uses the same core libraries but with a Swift frontend and is in TestFlight beta. I'm still waiting on Apple to approve the iOS release, among other things, before sharing more broadly.
JLCPCB is often the manufacturer of choice with DIY PCBs, and the reputation is well deserved. I recommend them as well, have never had an issue with what they've made. It's a bit pricier for a one-off board given the MOC, so it's preferable to do some sort of group buy if you can.
Slight tangent: a long time ago when I was into this hobby, Oshpark was usually the go-to instead of JLCPCB. What happened to them? Macrofab too if anyone's used them.
I don't think anything necessarily happened to OSHPark so much as JLC became the default for a lot of people. I find the defining factor is just consistency mixed with capabilities. Even if one could conceivably get a specific PCB stackup quicker from a US company, being able to order basically any type of PCB (and increasingly more than just PCBs) from a single vendor is a pretty significant value-add.
There are US shops like Advanced Circuits that can turn boards around extremely quickly, but obviously you are paying for that speed. Most people ordering a handful of boards for a hobby project, or prototype are probably optimizing more for cost and consistency than shaving a few days off the lead time.
Once someone finds a vendor where they know the quality will meet whatever their own subjective minimum is, there's not much incentive to shop around. Being able to tack on assembly at JLC with a single checkbox also exponentially increases the desire to just stick with that vendor.
Simple: jlcpcb can deliver you 10 boards for anything a hobbyist will likely need for 10$ including shipping, and it ships in 24 hours. Oshpark cannot compete with that.
OSHPark is bare board fab only but JLC does turnkey. I've enjoyed working with CircuitHub for turnkey prototypes. I'm not in love with the web interface (source files must be uploaded so if you have silkscreen that has dynamic parameters you need to make a ticket and the BOM parser misses stuff very often so every project needs an audit).
I have mixed feelings on this (I have some relatives in the medical industry). On the one hand, having a professional scribe is absolutely a positive for the provider, provided they have been trained and are accustomed to that provider. They take away significant cognitive load from them, leaving them able to focus on the patient.
With the proliferation of AI note taking, this advantage purports to have been democratized, but I'm not quite convinced. Since AI summaries are far from infallible, a mistake is bound to sneak in here and there (note that these aren't mere transcripts, but summaries split into sections). The provider may or may not go in and clean up your AI notes afterwards, any mistakes made by AI are effectively disowned in terms of responsibility, and admin will still pressure providers using these note takers as leverage to be able to see more patients than otherwise possible (admins want to see both lower costs and higher patients seen per day).
When you refuse this type of service, you're demanding a higher bar for your notes, but it comes at the cost of a distracted provider (who has grown accustomed to AI note taking, and only has so many hands, so they have to go back to the keyboard every now and then after checking your body).
In summary I think it comes down to how much you care about note quality versus care quality, which is likely different per person. I don't have any allergies, am not on any medications, and generally only go in for routine checkups, so in my case the notes are more or less a bureaucratic requirement that I'm happy to do away with cheaply. For others this may not be the case, and having quality notes may be critical to their care, in which case they should definitely refuse AI scribes.
Of course, none of what I said goes into privacy, which is a significant matter. However, "iPad scribes" which are essentially third party contractors remotely taking care of the notes already exist, so those concerns which arise even without the use of AI are a bit of a different topic.
AI only needs to be better than a human, which is also fallible.
But I would only accept AI note taking if it was reconciled (in a timely manner) by a human listening to the audio recording and verifying accuracy. Without that, it's an unacceptable loss of accountability. Even with that, privacy concerns are abound with frontier models.
STT local models offer different concerns, but generally are pretty good at transcribing in a quite environment.
Capitalistic pressures reduce quality of health care far too often. Everything from artificially limiting how many doctors get degrees, to pushing doctors to see more people per day from such tech. The enshittification will continue until moral improves.
I don't know about Yew but I've been using Iced 0.14 which is also a Rust crate inspired by the Elm architecture. It seems like Yew is specifically geared towards web applications, which I suppose is in some ways closer to the original Elm project.
What is your app? Is it intended for personal use, or commercial?
Nice! I'm quite the beginner when it comes to music production and theory (took me a while to even figure out "Audition" means "Listen"), so I couldn't make full use of this site, but I like ideas presented in your about section. The website is quite functional, which is nice to see from a Rust base.
I'm interested in looking at more commercial products made in Rust, they tend to be far more polished than what I can stumble upon in Github (and are thus a nice showcase of what a bit of polish can do for these frameworks).
I'm working on Totem (https://totemkb.com), a collaborative knowledge management system built entirely in Rust without any HTML or web-tech. Currently supporting Windows, MacOS, Ubuntu, and iOS (although the iOS build is currently in review).
Although the goal is to build an efficient all-in-one-workspace, I wouldn't run a company on it just yet. Right now I'm looking for early adopters who don't mind the rough edges and relatively minimal feature set.
The one major concern I have with this framework, and with rust UI frameworks in general, is accessibility. That's something you get for free or nearly-free in other ecosystems but seems to require a fair bit of elbow grease here.
Still, I would wholeheartedly recommend Iced, with the one caveat that it hasn't yet hit 1.0 and version upgrades could be a little painful, and might bring big changes.
[0] https://thinktotem.com
reply