-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixed length exercise session is a bit funny #428
Comments
The fixed number of words is worth reviewing in the future. There is a balance to find, and due to the randomness of selecting exercises, sometimes despite the 13 words we can select, some of them will be placed in a multiple bookmark exercise, where only one or two are reviewed. However, in this topic - sometimes I see that sometimes when doing exercises with for example 5 bookmarks there is a split of like 2 sessions. Personally, I think that now that we can just keep doing exercises and it's quite responsive it's OK, but tuning the concept of an "Exercise Session" is worth looking at. |
Having a look at this, I have found that it's all due to the fact we have introduced a few exercises that require 3 bookmarks. This means that out of the 12, if we have 2 exercises that require 6 bookmarks, we essentially will only practice 6 more (if they are all used in 1 bookmark exercises). I think since we currently we use a random assignment, it makes it somewhat inconsistent, where some sessions can be quite small. I think to solve this, we could attempt to not consider the extra bookmarks as "used", but this would mean that we could have some overlap with the bookmarks. Another alternative could be to increase the number of bookmarks we review, but we limit the Exercises (rather than the bookmarks) to make it consistent of doing at least 10 bookmarks each session. |
A simple solution for this might could be:
|
I think it's hard to say, obviously it's rather subjective what an exercise session should be. I think if we had a time objective for each user it would allows us to check - have they completed their 5 minutes goal for today? And base the decision from there. We can try to set the upper bound to 20 and see how that feels. I think in the current setup we could end with a very long review screen with 20 word sessions. Maybe in the desktop we could sorta have a two column design, the problem would still remain for the phone screen:
I think this could work. Personally, I don't think it makes so much of a difference to not show the words you got correct/wrong, maybe just adding the string above the buttons could be enough: |
Note that your wording with "Words progressed" and "Words that you'll need to repeat" should probably be kept irrespective of the horizontal layout on big screens, or if the layout stays the same! |
Yes, the little tiles it's part of the whole finding out a better wording for them. I think what we could do indeed is to have some way of revealing the words reviewed or going to a review screen, maybe that would make more sense. Maybe just revealing instead of loading a new page would make it snappier. Could be the idea of a collapsible component that we have talk in the past. I could look into developing that. I feel like it would fit here. |
collapsable panel... or just a visibility boolean would be fine indeed here :) |
Yes, that is essentially what the component would do! I will get it ready! |
I think I like more the arrows. Unfortunately, even with the collapsable component I find the message of the page a bit unfocused.
and if i continue, then i never get to see the word review? Do you see what I mean? |
My fear of leaving it uncollapsed is that the user wouldn't see the wrong words in a small screen - if we assume a situation where a user gets most words correct it's could be very likely they wouldn't see the wrong words. It seems to only make it more confusing to introduce a segment & session idea to me. I think it's fine to say that You review these words to now, and not worry too much about segment/session distinction for a user. If we are too worried about the time spent this session, we can just change it to "Time spent exercising: " and that would solve that issue. Maybe it would be more important to look at the words that are incorrect rather than the ones that are correct, so changing the order would be good? I think we also have an issue if we do this, then we also need to adapt the screen to say you have words that can be started to be practiced, because before it would just rely on the keep exercising. So to recap, I would keep the following:
Screen once all words are reviewed
I don't know about this screen, but we certainly have to think about a way to make it "flow" for a user. |
I also realized there is the matter of if you are reviewing a word a second time, and you get it wrong - you technically can review it in the same day - so you could have this screen appear and you are reviewing the same word. |
Uff. This is complicated. Y know what's the simplest thing? Create a
session with all their words. If they have 100 so be it.
Less code for us. And not work for the lazies. Win - win!
They can always stop before the end of the 100 words, and they will anyway
have a feeling of progress because of your badge.
…On Fri, 9 Aug 2024 at 11.58, Tiago Ribeiro ***@***.***> wrote:
I also realized there is the matter of if you are reviewing a word a
second time, and you get it wrong - you technically can review it in the
same day - so you could have this screen appear and you are reviewing the
same word.
—
Reply to this email directly, view it on GitHub
<#428 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADRNB74TIB5PSXPSQYRQOTZQSACXAVCNFSM6AAAAABK4XI7CKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGQ4DIOBTHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
And wrt. Therm not seeing the wrong words... Put those at the top?
On Fri, 9 Aug 2024 at 13.55, Mircea Filip Lungu ***@***.***>
wrote:
… Uff. This is complicated. Y know what's the simplest thing? Create a
session with all their words. If they have 100 so be it.
Less code for us. And not work for the lazies. Win - win!
They can always stop before the end of the 100 words, and they will anyway
have a feeling of progress because of your badge.
On Fri, 9 Aug 2024 at 11.58, Tiago Ribeiro ***@***.***>
wrote:
> I also realized there is the matter of if you are reviewing a word a
> second time, and you get it wrong - you technically can review it in the
> same day - so you could have this screen appear and you are reviewing the
> same word.
>
> —
> Reply to this email directly, view it on GitHub
> <#428 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADRNB74TIB5PSXPSQYRQOTZQSACXAVCNFSM6AAAAABK4XI7CKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGQ4DIOBTHA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
For those that have 100 words we can simplu display an info box - "these
are a lot. You don't have to finish. Do as many as you can and you'll see
they decrease"
On Fri, 9 Aug 2024 at 13.55, Mircea Filip Lungu ***@***.***>
wrote:
… And wrt. Therm not seeing the wrong words... Put those at the top?
On Fri, 9 Aug 2024 at 13.55, Mircea Filip Lungu ***@***.***>
wrote:
> Uff. This is complicated. Y know what's the simplest thing? Create a
> session with all their words. If they have 100 so be it.
>
> Less code for us. And not work for the lazies. Win - win!
>
> They can always stop before the end of the 100 words, and they will
> anyway have a feeling of progress because of your badge.
>
> On Fri, 9 Aug 2024 at 11.58, Tiago Ribeiro ***@***.***>
> wrote:
>
>> I also realized there is the matter of if you are reviewing a word a
>> second time, and you get it wrong - you technically can review it in the
>> same day - so you could have this screen appear and you are reviewing the
>> same word.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#428 (comment)>, or
>> unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/AADRNB74TIB5PSXPSQYRQOTZQSACXAVCNFSM6AAAAABK4XI7CKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGQ4DIOBTHA>
>> .
>> You are receiving this because you authored the thread.Message ID:
>> ***@***.***>
>>
>
|
Okay , yes - I don't see why not! At least it's worth a shot! :)
That's what I am doing now! I think it can work - let's see! |
There is just one thing I realized - if the user has 50 words already, maybe we should say a little warning before keeping to exercise ? But I think I like it! |
"removed the limit" means that now if I have 40 words due to day, i do all of them at the same time? this conversation got so long that I've a hard time following! |
Yes, that's what I meant by removing the limit, now the user will get all the words that are scheduled without a preset limitation. Now, the only thing I am trying to figure out is how to explain to users that they might have extra words to learn besides the ones that they have scheduled. In this situation, there are also 2 possibilities: Either they are at the limit words they have to learn (which we set at 50) or not, where they could just start learning more. But I also think this can be a bit confusing. Maybe the easiest is, if no exercises are detected I just show the "Back to reading" message rather than "Keep Exercising" |
Love this Tiago!! In case 1: why do we have "keep exercising" if the situation is "there are no more words for you to practice"? Or is the situation: In case 2, does the code get more complex if the button becomes: In case 3, could the button become: In case 3 we're in this situation because the user got four words wrong, right? Maybe we could say that explicitly? All these above are minor observations, so feel free to handle them quickly and send a PR when you want. After all, this feature should also be usability tested with users for better fine-tuning :) |
This was an oversight, in case one we should just have the Back to Reading button.
I think this would be nice and I have done this now. I had to increase the button size slightly, but it still looks OK.
There could also be the case where a word progresses into productive knowledge and the user can do it right away. I had thought about the possibility of always repeating the ones you got wrong, but I think that would mess up with our schedule too much. If you are at stage 16 and go back to 8 you don't repeat the word immediately for example. While working on this I have also given it some thought, and I still think maybe it is good that sessions aren't extremely long (> 20 words) as I have seen my girlfriend go over words at the revision stage, and if there is many words I think this revise step might be a bit too overwhelming. Like you say, we can maybe do some testing before rolling this out completely, but I like informing better the users about the learning new words/words that are due to study. I am updating the screenshots to the current state of the branch. For clarity, I have also decided to just say Words Correct and Words Incorrect to simplify the language there as well (this is shown in screenshot 3).
|
Cool! I wonder... can we make it more forward-looking? Instead of "back to reading" we could simply say
Agreed!
Fair enough.
That's a good point! I think with the current setup we could do a 20words session.
Looks cool! And yes, |
today i had 14 words to practice.
i did one session, and I am in the following situation:
there are still three words to practice. my thinking, as a user is: why weren't they included in the practice? i wonder what's the simplest way to solve such situations?
The text was updated successfully, but these errors were encountered: