itch.io

Appreciate you taking the time to respond, and good to hear directly from the team.

I've been using 4.0 for a few days now and it's noticeably smoother than what I was running before — the rebuild clearly paid off. Worth the work you put in.

For what it's worth, my original gripe was never really about the timeline itself. A rewrite this big taking a while is completely understandable, especially for a two-person team going in blind on most of the API stuff. The frustration was mostly about transparency — going quiet on where things stood while the hype kept rolling.

So if there's one thing I'd genuinely suggest going forward, it's keeping the community a bit more in the loop. Even a rough "here's where we are, here's what's blocking us, no firm date yet" every so often goes a long way. For me at least, the silence was harder than the wait itself.

Glad to hear you're back on a healthier, scheduled cycle too — that matters as much for you not burning out as it does for us. Everything seems to be heading in the right direction. Thanks again, and looking forward to what's next.

Alright, let's be honest about where we're at with Cider 4.

I've been a Cider user for a while now. I genuinely like what this team has built — it's one of the few Apple Music clients that actually feels like someone cared about the experience. So this isn't a hit piece. This is a fan talking.

The Cider 4 feature list looks great. MKLite audio engine, Dolby Atmos, a fully rebuilt queue, dropping MusicKit.js — this is exactly the kind of ambitious update that makes you think "okay, these people actually know what they're doing." I read the changelog. I got excited. That was back in March.

It's now June 2026.

The X account is still active. Screenshots still look polished. Dev updates still sound positive. And yet — no release date. Not a beta. Not a quarter estimate. Just a steady stream of "we're really happy with where things are." Back in February they said release planning was "soon approaching." I'm still approaching it too, apparently.

Look — I get it. This is a small team doing a massive rewrite. Nobody wants a broken launch. But there's a difference between "taking the time to do it right" and "going dark on timelines while keeping the hype alive." One builds trust. The other slowly drains it.

I'm not angry. I'm just tired. Every post reminds me of a product I want to use but can't. At some point, that enthusiasm you've built up in the community starts converting into indifference — and that's a much harder thing to recover from than a delayed release.

Drop a beta. Set a rough window. Acknowledge that the wait has been long. That's all it takes.

Still a fan. Still waiting. Just... less excitedly than before.