Help us improve Anki

I think that while reviewing, Anki should show the tags associated with each card. I use tags for important context, like the general subject of the card, that would be inconvenient to put in the text of each card.

I know that I can do this by editing the templates for all my card types, but it seems kind of ridiculous that I need to go through all these steps and write my own HTML to be able to do this. Doing this is kind of tricky and annoying for me, and probably incomprehensible to someone unfamiliar with HTML and CSS.

I think this should be a setting that can be enabled and disabled via a checkbox, and arguably enabled by default.

Have the ability to remove duplicate cards easily by using the browser option or similar

This is a {{c1,c3::example}} of a built-in native {{c1,c2::cloze}} {{c3::overlapper}}

cloze 1. This is a [...] of a built-in native [...] overlapper

cloze 2. This is a example of a built-in native [...] overlapper

cloze 3. This is a [...] of a built-in cloze native cloze [...]

After some time if nobody download a shared deck / addon it is automatically removed. I don't think it is a wise feature. I wanted to download some very well rated deck but i found it deleted

• add languages in which is written
• add topic or multiple topic at once
• add thumbnails

Right now there's only 4 flag options. I could really use more to stay organized!

I know it's possibile to do it with workarounds but it still have some bugs and slowdown that way. Would be much better with a built-in native function

Add the ability to choose which decks are for sync and which are not for

Would be awesome to be able to edit cards without opening the browser, and make simple corrections/additions from the reviewer

Would be dope to download customized note types with HTML, css

When we paste an image, have an option to resize it before it gets saved onto the card.

if a card has multiple cloze deletions, instead of having separate cards for that --make it so that you test on the card and not the cloze deletion. For example:

if you have

{{c1::x}} + {{c2::y}} = z

if you guess x wrong, then instead of testing on c1 again --when you see it again, it tests you on y. So you're not testing the cloze deletion, but rather testing the card or core concept. This lightens the amount of workload a person would have without sacrificing too much.