The app doesn't recognise when users mistakenly translate instead of transcribe
Users used to be given a second try when they mistakenly translated instead of transcribed. Why is this no longer the case?
Also, a lot of users don't understand what they did wrong. If there's no plan to give users a second try again, the copy should probably be changed.
Here's a collection of tweets by confused users:
There are tons more.
On a related note, here's another example where the copy should be changed to explain they were meant to select ALL correct answers, not just one.
This was a very neat and useful feature; I was translating rather than transcribing audio all the time when I started using Duolingo. They should certainly bring it back.
Also, a lot of users don't understand what they did wrong. If there's no plan to give users a second try again
Back in time, for "write [in target language] what your hear [in target language]" exercises Duo was displaying the message
Wrong language! You need to listen and type in XXXX.
while giving you a second chance.
If the second chance isn't to be given back, they really should put back this message (which is till defined in the database, just not used anymore): it'll allow to know why our answer is wrong, hence to get frustrated and not reporting our answer as correct (while, it's indeed not correct).
In addition, in order to help us knowing in which language we have to answer (whatever the type of exercise) even if we not look carefully to the screen, I think that adding a flag would help. Something like:
instead of the current:
Someone knows if it disappeared with the release of the new version of the website or if its disappearance is independent?
If the former, there is a hope for it to be one day put back(*).
If the latter... almost no hope, IMHO.
(*)and it could be added (by staff) in this list.. we'd know if they plan or not to add it back ;)
It can be confusing when you are so keen to give the answer you do not read the question carefully. It has happened to me and lots of other users, but the answer is not to add extra code to explain why they got thing wrong, but for the user to slow down and read the question correctly.
but the answer is not to add extra code to explain why they got thing wrong
Such "answer" already exists in the Database and was present in courses before. ;) So it's likely(*) not that much work to put back this message as it was before.
And, IMO, it's part of the answer/solution as it'll reduce the number of (false) report contributors will receive, which will give them more time to take care of "true/real" reports. But, of course, in parallel, we all should slow down. If not when answering, at least before reporting. ;)
(*) but maybe I'm wrong and it's really long and hard to link back the existing message in the Database (already existing in all languages) to the website, in which case there are probably higher priorities.
It will be interesting to see if this changes one way or another. Different parts of DL seem to support different mechanisms, i.e. I am fairly certain that the website UI for a native English speaker learning German will give you another chance to transcribe if you translated, while native Germans learning English do not get this. It would be typical of DL to run an AB test to see which mechanism had the best learning outcome.
From my perspective, the objective of the site is to teach translation, and when a user has correctly heard and translated a sentence, they ought to be recognized for achieving the goals of the site. Also, the design goal of a UI should always be to guide a user to accomplish the objective without having expend extra mental effort on determining what the objective is.