Decks Audio


(Olaf Rabbachin) #21

Did you know that you can mark postings as solution to your original problem? This way they’ll also be highlighted, which helps others looking for a solution to the same problem.
FWIW, even when sticking to the original topic, threads can get quite confusing which is why the solution-attribute is a great means to let the right postings stick out.

P.S.: And sorry for posting off-topic stuff in your thread, it just happens every so often!


(Amanda Norrsken) #22

I’d be so happy if this WAS solved one day soon!

It is so frustrating as a course contributor who has worked really really hard on improving definitions and removing old, not very good, or simply wrong definitions, to see them pop up in multiple-choice boxes :frowning:


(DW7) #23

Hi there @robotlb & @duaal, I’m afraid a lot is going on very quickly and it is getting confusing and onto multiple topics.

I agree, having had time to read through, that it has also developed into a “communication” issue and a separate thread would be a good idea.

However the trouble is that some posts should be in both threads and one can not duplicate.

As @kevin5284 has posted some great comments here, I think he would be best placed to decide which posts to move and where (please).
Or perhaps he can create a new thread about communication and repost (by copy & paste) to that one.


(DW7) #24

I think a lot of people have said that in effect or directly.

Perhaps there is a role for the planned web decks to be free but a new separate app with development, upkeep and with download function to be paid for.

Although this would obviously have to come after the “D” (for Decks) day as ‘all hand are on deck’ (no pun intended) for that.

Cc @kevin5284

PS sorry this is off-topic too - guilty as charged!


(Memrise Matty) #25

I agree It can be frustrating when one of us does not respond in-terms of legitimate bug reports or issues. Myself (Support) does try and respond to some cases, but the reality is this forum, and specifically the bugs section, should be managed by multiple staff members. Which unfortunately (due to some of the reasons mentioned by Kevin above) is not currently happening. Thus some threads get overlooked.

In terms of this specific bug, Support raised the issue internally in Oct 2018 but has not seen any progress on it. It’s safe to assume this has been classified as a low priority issue. I will update the relevant thread now, and again when we get an update on it’s progress.


(Fisher Lanham55) #26

This is a great response.

Kevin has been good throughout this, especially recently when the canned responses have been put aside for much better ones, but I still admit I am not the most sympathetic with Memrise here. There are angry users, indeed, but there are also lots of very respectful users that are still being answered only with silence and their feedback not being addressed. It gets tiresome to speak up over and over again about issues without any acknowledgement. That’s why people are angry, not simply because you are making changes at all (there will always be reactionary nuts that resist any sort of change, even good change).

Memrise has been extremely unpredictable in the past, and as seen with Decks, continues to be. It’s also the job of a company (especially a consumer-oriented company) to solve communication issues with its users, not the other way around. There are many examples of consumer-oriented companies with excellent track records on communication that can be copied.

It all reminds me a lot of this quote from the simpsons:

So as this user said, it’s a Catch 22, but it is your job to fix it, Memrise. Many of the long term users here are want to help give great feedback and fix the app that they and myself have grown to love. It has become an integral part of my language learning.

Thankyou for your communication efforts in this past week. The meeting set up tomorrow was a great idea; I only wish I lived in London and could come. Ed even personally responded and liked my tweets to him, which I thought was great and showed commitment to listening.


(Hombre_sin_nombre) #27

I like very much how Olaf did in the other topic: you could see almost every Android bug in one post. This is very convenient.

My suggestion to you is to create a few topics for bug reports (web, iOS, Android, other complains), start every topic with already known bugs, advise users to read them first before reporting a bug (in case the bug is already listed and there’s possible solution) and subscribe your staff members to relevant threads, so they could follow up them easily.

Well, if my idea is not that good, then you can do it in your own efficient way. This board is sure a little bit out of order and you could overlook something.


(Memrise Matty) #28

Thanks for the suggestions. We do have a bugs section for Android, iOS and Web here: https://community.memrise.com/c/bugs

There is also a “Known Limitations” section where we have created a list of Known Bugs which have not yet been fixed. I just updated it with the Android / Web issue we discussed above: [WEB-783] Words learned discrepancy on (Web/Android)

I will do my best to update the Known Limitations section where possible, and hopefully more members of the team will take more of an active approach to these other bug sections in 2019.


(Olaf Rabbachin) #29

If there is one or more bugs missing on my list, feel free to post them on the thread, I’ll then update the original post. I’d sure like to have them all in one place!

@MemriseMatty: that’s exactly where I post all bug-reports that I’ve come across for Android. I also went ahead and filled out several “official” bug reports. The latter link is following this official help article regarding bug-reports.
If there’s a better way to transport such information to you guys, I’d sure like to know.


(Memrise Matty) #30

We do monitor the bug reports that come in via Support, and we have raised a number of internal tickets for these issues. We will continue to update the Known Limitations over time.

Our QA team, and QA Lead @JBorrego, are the ones who should be monitoring the bugs section of this forum. Hopefully they can enlighten you further…