Familiar is useful.
We use SwiftUI and the controls, animations, and transitions Apple provides. A custom experience needs to offer more value than the native one.
OUR APPROACH
Own your setup.
Enjoy using it.
The service is only half the experience.
We build the clients we want to use with it.
WHY WE STARTED
Every client left
something missing.
When we started self-hosting our media, we tried multiple music clients for Jellyfin and other services. Some were crowded and complicated. Others were so stripped back that useful features were missing. A client might look good on an iPhone but have no Mac app, no CarPlay, or controls that were awkward to use.
The most consistent frustration was simple: we wanted apps that felt native to Apple, including a real Mac app. We couldn't find the complete experience we wanted, so we started building it.
Reading had its own problems. There were fewer clients to choose from, and too many required clunky OPDS setups before we could get to a book. LibraVia starts with a different expectation: sign in to your server and start reading.
WHAT GUIDES THE WORK
Use what Apple already gets right.
Finish the everyday tasks.
Playing music is a start. Offline listening, playlists, AirPlay, and a manageable queue make it useful in daily life.
Build for our own use.
Jellyfin comes first because it's what we use. Apple comes first for the same reason. Our own needs keep the work grounded.
Make it great to use.
Being better than another client isn't the goal. We want these apps to be good experiences in their own right.
PRIVACY
Your data isn't
our business.
We have no interest in collecting your personal data. We handle privacy with the same care we'd expect for our own credentials and media.
The apps do not send analytics or debug reports automatically. A debug function includes an explicit share option, so you decide whether to send that information. TestFlight builds also include TestFlight's basic feedback reporting.
Connecting to your media server is part of using a client app. Sending information to us is a separate decision, and should be a knowing one.
WHERE WE'RE GOING
Jellyfin first.
Room to grow.
We've used Calibre, Booklore, Storyteller, and other services for books. We want the freedom to choose the service that fits our media best, rather than choosing a service just to keep a particular client.
More modular library and service handling is part of our plan. Support for other self-hosted services is a direction we're working toward, not something the apps offer today.
Web support is planned before support for other operating systems. Roadmaps are on GitHub, and they evolve as we discover needs through our own use.
Follow the work on GitHub ↗Feedback matters.
So does focus.
We read all communication. We reply and act as our decision-making process allows. Not every request will become a feature, and the roadmap will keep changing as we learn.
Explore the apps ↗