App Improvements

[YuriDevAT]

Let's discuss about improvements to the app to assure good user experience 👇🏽

[YuriDevAT]

README

The README is currently used to store general information which can also be found on other project in this organization as well. The Readme should be used solely to share this projects information.
👉🏽 Please read more on this thoughts in the general discussion https://github.com/orgs/YurisCodingClub/discussions/34

[CorinaMurg]

SUGGESTED FEATURES

I would love to suggest a few features for the app. These are definitely more than we might have time to implement, so no pressure!

1. A counter that tells the user how many tags they have entered.
2. A congrats message if they entered a certain number of tags already (let’s say 50, 100 ..) or how many left until a complete list
3. Or, a congrats message if they entered all the tags that start with a certain letter (Congrats, you have now entered all the a-letter tags!)
4. Hints that are revealed when the user clicks a button. (I know, it’s a quiz, so maybe we should not help, but sharing the idea anyway in case it might inspire related features.) For example: total number of tags, number of tags that start with a certain letter, which letters of the alphabet are NOT used to start a tag, etc.

Done! (for now 😊)

[YuriDevAT]

I think you can start it anytime. Also, no apologies, it was simply a suggestion 😉 Side fact: I only know about Draft PRs through The Collab Lab' last cohort!

Apart from a description, what else should it have

I think that's what makes a Draft PR, because you start with what you have and improve it on the go. But I could be mistaken here.

[CorinaMurg]

We started the conversion about the progress bar here, but is the page for the issue itself more appropriate to ask specific questions? Especially now that we have a draft PR. Or should it be on the PR page, right at the bottom? (Still learning to navigate the GitHub space, thank you for being so patient with me 😃)

[YuriDevAT]

Excellent question. I guess the draft PR seems a good place, because we both can directly add a comment to specific parts of the code? I will check what common reasons for a draft PR are.

Here in the discussion I think it makes sense to discuss things which are not decided (are an issue) already. But I am learning too, so I am open for any suggestions. This is only my experience so far.

[Dorstener]

1. I really like the idea of the progress bar and I see that it is already being worked on

2 & 3) The idea of having a "milestone checkpoint" ("you reached 30% of all tags") or something like that would be very nice. Here I would like to add an idea. I am not sure if there are stats on which tags are used more or less than others. I asked this, because it would be cool to have a feature in which if the user adds a tag that is in the "not so used" list, he/she gets a comment like "Congrats, you just added one of the most unused accessibility tags". Something like this, kind of a gamification on the usability of tags.

[YuriDevAT]

I like that idea. I actually don't know which tags are used not that much. I mean, in general I know which at least should be used in almost every project, but in terms of which at least, especially compared to others seems interesting to me.

[Dorstener]

Hi team,

Hereby my suggestions for the app:

Once the user cannot input any more tags, a final submission should be done. It would be great if it gives him a final score, with a breakdown on the category of the added tags and a final rank in comparison with other users (even maybe do a like a badge category - "Accessibility Master" and so on):

Example

You successfully added 15 out 50 accessibility tags:

you added 11 out of 35 most used accessibility tags
you added 3 out of 10 sometimes used accessibility tags
you added 1 out of 5 never used accessibility tags
You rank 37 out of 289 users that took the accessibility quiz. CONGRATULATIONS !!!

Together with this "end of quiz page", it would be great to have a section with the missing tags for that user _(encouraging learning opportunity) _
"Would you like to know about the missing tags"

And here the user can click, get a list of all the tags he/she did not select and when the user clicks on one of the tags of the list, it will provide him/her with:

• Description of the tag
• When to use it
• Example of usage

[YuriDevAT]

I really like that idea. Thanks for getting into more details on this.