Your part in shaping Muttr

Muttr wouldn't be what it is without the people actually using it.

I can build something, test it, break it, fix it, test it again, and think I've covered every angle. Then one of you uses it in a way I didn't. That's not a bad thing. That's part of building Muttr.

You're seeing the real thing

Something I don't think I've ever made very clear is that Muttr is built and maintained by me. Not a development team. Not a QA department. Not a support team behind @MuttrStaff.

Just me.

I obviously test what I build before putting it in front of everyone, but there's a huge difference between me testing something and hundreds of people actually using it across different accounts, devices, settings, communities, and situations.

Eventually, someone is going to find the weird combination I didn't. And when you tell me about it, I can usually do something about it.

That's exactly what happens

A couple of issues get reported such as:

• Creating a community could fail with a permissions error
• Some users couldn't edit their own comments

I tracked down both and fixes for both are now live.

That's the part I want people to understand. Reporting something that's broken isn't annoying me. You're not wasting my time. And you don't need to know why it's broken before saying something.

If something doesn't work the way it should, tell me.

Sometimes it'll be an actual bug. Sometimes it'll be an edge case. Sometimes you might point out something that technically works exactly as designed...and make me realize the design itself could be better. All of that is useful.

You're helping shape this place

Muttr is still growing and changing.

A lot of what gets improved doesn't come from me sitting around trying to guess what everyone might need. It comes from watching how people actually use Muttr, seeing where something creates friction, listening when something doesn't make sense, and fixing the things that don't hold up in the real world.

That's where you come in. When you find something weird, report it. When something feels harder than it should, say so. When you have an idea that would genuinely make Muttr better, throw it out there.

I won't promise every suggestion becomes a feature or that another bug will never slip through. But, I will keep paying attention.

Found something?

@MuttrStaff is still the easiest way to get my attention, or you can post in Muttr Support.

If something isn't working, just tell me what you were trying to do and what happened instead. If you saw an error message, include that too. You don't need to figure out what's wrong or explain it like a developer. Just tell me what happened and I'll take it from there.

You use Muttr in ways I never could by myself. And whether you realize it or not, you're helping shape what Muttr becomes.