zeeguu / web

Frontend for the zeeguu web application.
https://www.zeeguu.org
4 stars 7 forks source link

confusing situation #537

Open mircealungu opened 1 week ago

mircealungu commented 1 week ago

i read an article. translated two words. learned that Pacific Ocean is Stillehavet:) Which is cool!

Then ended up with this confusing situation:

image

I am just left with a feeling of I'm doing something wrong, w/o having the chance to improve the situation. The "we recommend that you at most learn 50words" sounds too threatening. And there's nothing I can do about it. Should we omit this maybe?

One actionable thing that we could do is to make the "53 words" a link that would link to the Learning words page. The problem is that we have two tabs at the moment so it would not be clear to which of them to link. One more argument to revive the discussion on Learning vs. Learned and propose again that we only have two tabs there: Learning and Learned. And the various stages in Learning can be page divisions, but not tabs.

If one could go to that page, then she could also do something about it, e.g. investigate the words that are being learned, and maybe delete some of them, e.g.

What do you think @tfnribeiro @igawaclawska @merleschoen ?

tfnribeiro commented 1 week ago

We definitely don't want to threat the user / make them feel they did something wrong, but I also thought that we want to make sure users don't get into a point where they have 100 words and might never learn a single one!

I think the solution might to somehow create an interaction that allow you to remove words from the pipeline similar to when a user translates more than 10 words in a single reading.

Now, this interaction won't be so easy to implement - I think having Learning VS Learned would help - then you could have a toggle in learning to remove words from the scheduler. However, I think we would have to rethink a bit what information we then give about the state of each word. Maybe a slightly different word preview?

A very rough draft could be:

  1. Remove the Speak button, and instead make the word clickable - this would mirror what we talked about in the exercises. Since these are not in context we would assume a click == pronounce.
  2. We can use the collapsible component to separate Receptive / Productive into two categories. The info could be shown either by allowing users to click on the Receptive / Productive word or by having a small ? next to allow users to see the question
  3. A toggle which allows users to quickly remove words from the exercises they don't want.
  4. We could add a little line saying the recommendation of 50 words max - in a friendly way to incentivize users to customize the list as they go.
  5. In this interaction we might want to also display words that are "waiting" to be learned, AKA in case you haven't started learning them or are over the limit.

image

tfnribeiro commented 1 week ago

I had another thought that maybe it would be also nice when editing that we could do a - "Recommended" sort of option.

This would just add the words based on their frequency list until we fill the 50 words for example? We could even say why we didn't pick the words that were deselected.

mircealungu commented 1 week ago

At a first glance, I really like the "waiting to be learned" words idea! :)

mircealungu commented 1 week ago

I didn't understand the "Recommended" option though. Let's talk about it in person?

tfnribeiro commented 1 week ago

I didn't understand the "Recommended" option though. Let's talk about it in person?

Sure!