Every piece of feedback gets read. There’s no triage team, no ticket queue, no autoresponder pretending to care. There’s the person who wrote muwav, reading what you sent.
Single issues (put a log on it)
muwav for iOS has feedback built in. Use it — it’s the fastest route by far. You can send it in the moment, while the thing you noticed is still on screen and fresh in your mind, and it lands directly with me.
There’s a quieter superpower too: feedback sent from inside the app includes the app’s logs automatically. That means no back-and-forth of “can you tell me what version you’re on” or “what were you doing right before it happened” — the answers usually come along for the ride. If you want it fixed, put a log on it — then I’ll propose a fix.
Bug reports, feature requests, “this one detail delighted me,” “this one detail drives me insane” — all of it comes through the same door.
On macOS
A built-in way to reach me from the Mac app is being reviewed. Until then, email works: support@cedarsyntax.com.
For bug reports, two things make a world of difference: your macOS version, and what you expected to happen versus what actually happened.
What happens to it
It gets read — all of it. Bugs get hunted, and the logs that came along often mean they’re caught on the first try. And if you just wanted to say the app made your commute better, that gets read too, probably more than once.
What about feature requests?
Here’s the honest answer: muwav is stable, but it’s not mature. There’s a long list of things it’s already supposed to become, and it’s not there yet. Until it is, feature requests mostly land in a drawer — not because they’re bad, but because the app needs to finish becoming itself first. So if you’ve got an idea, hold onto it. Once muwav is feature complete, that drawer opens. Your idea will be a lot more useful then — and so will the answer you get back.