Constructive criticism: more error messages please!

Hi Mudita Folks,
I just wanted to
a) provide some constructive criticism AND
b) thank you listening - i’m sure you’ve got a lot on your plates.

One gap I’m seeing as a user is that many failures do not have error messaging a user can start troubleshooting from. In the linked Mudita Center file manager topic, a group of users (myself included) get a blank white screen when trying to load the file manager tab. As a user, any kind of error message would be a better experience because it would let me search the forum for something concrete. Trying to come up with words for the feature that’s broken and how it isn’t working is a hassle. And an error message indicating the phone OS just needs to be updated would save all of us some pain.

In an unrelated experience earlier today, the forum blocked me from posting or editing. I got undocumented 403 errors when I included the name of a common linux directory. That was similarly frustrating - not only because I couldn’t post the thing, but because I had no idea why I was barred from posting. I had to cycle through logging out and back in, search for discourse 403 posting errors (because this looks like a Discourse forum), and then chunk up my nice post piece by piece until I found the issue.

As both a dev and a user, I know you folks are all working hard to make this a platform that’s easy and pleasant to use. Error messages are a great way to move in that direction. They’re usually quick to add, they can reduce the feeling that “this is just broken”, and they help user communities self-solve issues which can unlock time for you to invest in important features and fixes.

I appreciate all of your hard work making this platform a reality,
Chris

2 Likes