After earlier work with Synphonyte on complex browser-based medical software, I had the opportunity to collaborate with them again on a new set of projects.
One of the most meaningful parts of that return was my contribution to leptos-use, an open source library in the Rust ecosystem inspired by tools like React Use and VueUse, but built for Leptos.
That mattered to me for more than one reason.
First, it gave me the chance to contribute publicly to a company and ecosystem that strongly values Rust.
And second, it gave me a visible, verifiable way to show that my Rust knowledge was not theoretical. It had been tested through real collaboration, both in this open source project and in additional private work I contributed to with Synphonyte.
Why leptos-use matters
The idea behind leptos-use is simple and strong: collect essential utilities that solve recurring pain points in frontend development with Leptos.
That makes it valuable in the same way libraries like React Use or VueUse are valuable.
Not because they are flashy, but because they help developers solve common problems faster, with better abstractions and less repeated effort.
The project is public on GitHub, where it currently shows broad community activity and adoption, including hundreds of stars and forks. At the time of writing, the repository shows 459 stars, 100 forks, and 21 open issues.
Source: Synphonyte/leptos-use on GitHub.
Why this experience mattered to me
This was not only an OSS contribution.
It was also a signal in my own career.
Coming back to Synphonyte for new work meant continuing a relationship with a company that operates at a high technical level and has a real affinity for Rust. Contributing there again — this time with open source visibility — reinforced that I could create value not only in JavaScript-heavy environments, but also in a Rust-based frontend ecosystem.
That is an important distinction.
A lot of developers say they know Rust.
Fewer can point to actual collaboration on public Rust tooling that other developers can inspect, use, and build on.
For me, that made this contribution especially meaningful.
What it says about my technical range
By that point in my career, I had already worked across:
- public health systems
- medical imaging web applications
- distributed international product teams
- consumer applications for the US market
- industrial platforms for German clients
Contributing to leptos-use added another layer to that range:
frontend engineering with Rust, in public, inside a real ecosystem
That matters because it connects two things I care about deeply:
- building practical developer-facing solutions
- working with modern tools that push frontend development forward
What I value about this kind of work
One of the things I like most about utility libraries is that they usually come from repeated real-world friction.
They exist because a team solves the same class of problem often enough to realize the solution should become reusable.
That is a kind of engineering maturity I respect.
It means the code is not just written to work once. It is written to become useful again.
That is also why this project felt like such a natural fit.
It reflected the same kind of thinking I value in product work: solve real problems, remove friction, and build things that help other people move faster with more confidence.
Looking back
This contribution was an important milestone for me because it made one thing much more concrete:
my Rust experience had moved beyond curiosity and into proven collaboration.
Not only in private projects, but also in open source work that lives in public and contributes back to the ecosystem.
That is the kind of experience I want more of:
practical, well-grounded, ecosystem-aware work that creates value both for products and for the developers building them.