My media is already one collection, but using it means crossing a chain of unrelated apps: discovery and requests, acquisition, metadata, files, then playback or reading. Each handoff repeats identity, setup, state, and troubleshooting.
I m building Prismedia around the opposite idea: the movie, book, album, or audiobook stays the same item from the moment someone wants it through acquisition and finally watching, listening, or reading it. The server and web workspace are self-hosted, with native iPhone, iPad, and Apple TV experiences on top.
Before launch, I d love concrete feedback from people who run their own media stack:
Which handoff loses the most context today?
Would a unified operations workspace or a better native consumption experience matter more to you?
What would an app need to prove before you trusted it with more of the lifecycle?
Finally something that treats audiobooks and comics as first-class citizens instead of an afterthought. The metadata fix workflow felt surprisingly smooth on my messy library.
@warren_fei Glad to hear, the core of this app was to bring the same level of support TV and Movies seem to get to music and books etc, all are very similar in function and management, but the current suite of apps is scattered and not maintained. Please let me know any feedback as the app is still early
Self-hosting a library across Sonarr, Radarr, and Kavita always felt like juggling tabs, so I'm curious to see if Prismedia can actually glue it together. The request flow into acquisition looked smooth in the demo, and the cross-format progress tracking is the kind of thing I've wanted for years.
@derrickrose That is exactly the goal of this app, let me know what you think and I will continue to pull things together, but the core app is strong and consistent between all media types.