Right now, when no results are found, it says nothing.

We should add icon + "no results found" + "clear filters"

言う is translated to "to go".

The third stroke of 鹿 seems to self-intersect or something. Doesn't have any effect on the ability to draw the Kanji though.

I was hoping to find an address to e-mail the team at to ask this so I hope this doesn't feel too mean-spirited to say publicly. I've enjoyed using this app so far, it's an incredibly useful tool, but the apple on the main page unsettles me greatly. While I don't doubt love was put into its design, something about it's small pupils and wide-set smile give the impression it wishes to do me harm (as I'm typing this I have the app open to my side and I've just seen it switch to its angry expression for the first

For 否 in the example for no it shows the hirigana ひ instead of いいえ. However it is still pronounced in the audio as  いいえ.  

See https://ibb.co/M89QHqy 

In the base kanji 木 the middle vertical stroke is quite strict. This also occurs when it is a component. If the stroke is done fast it sometimes registers it as not crossing into the second quadrant and marks it wrong. 

hey :) i really like this app so far. my ability to write and recall kanji has increased a lot and it's given me a boost in motivation to keep learning japanese again

however there is one slight frustration i've been having with a particular kind of stroke ^^' the ム stroke in the following images appears to be strangely unforgiving, and i feel like it might be a bug, especially since for one of them i was completely in the line

https://cdn.discordapp.com/attachments/169822079091212288/1216586856225837086/IMG_4775.png

https://cdn.discordapp.com/attachments/169822079091212288/1216586855126925412/IMG_4783.png

https://cdn.discordapp.com/attachments/169822079091212288/1216586856615903262/IMG_4774.png

https://cdn.discordapp.com/attachments/169822079091212288/1216586857094058054/IMG_4772.png

i do have the stroke accuracy set to "strict". i don't know if that

Reported as a comment here

When reviewing 斤 there is just single usage provided: きん which is translated as "kin".

Hi,

i have been using ringotan as a drill app and to learn kanji at my own pace using the custom review. 

Noticed that there is 1 missing kanji in the Katakana section.

My lesson plan is JLPT.

Possible to get a fix for this?

Audio for first word of kanji 輿 is かご but should be こし

Supposedly they do.  If I can replace all the icons with their SVGs, this would save space + time, and would look better.

Is there some way to search across all the Kanji supported by Ringotan? I'm trying to find the 旧字体 version of 亀 (龜) which is listed on KanjiVG but I can't seem to find in any of the lesson sources (including JLPT and Kanken)

PS: Absolutely loving Ringotan, thank you so much for making this!

A handful of jinmeiyou kanji aren't used in any actual words (making them not currently supported). And a lot of the ones that are are so rare we shouldn't be using them as prompts.  It'd be better to use names for prompts instead, the way they're actually used.

Some examples: 燿藥覽偖凭剌哥嗽嘸嚏囀嫋屹掏捩焜犇皰稍窶綽罅聊臘蜀齎跣踉蹌軈閊靨鞦韆飩饂暝

I have seen others post this idea already, but the more feedback the better, right? 

The first idea is that your own handwriting is on the screen. Maybe until you make a mistake or until you complete a kanji. The specifics aren’t that important to me. Just swing your own handwriting until you finish a kanji is what I would absolutely love for the app to have. In my opinion you can’t cheat that way and you feel like you actually did write it all by yourself. 

The second idea is that since most kanjis have multiple readings, there could

It would be nice to have an option to start by directly prompting a kanji with an empty canvas, and only going through the learning steps if we mess up on the first encounter.

For people that already learnt kanji by recognition (which should be a majority), this would speed up the learning process tremendously, especially for the simpler kanji.

Not something I want to do, but something I have to do, since Microsoft is dropping support for Xamarin...

Need to figure out a way to do this without a bad user experience. Idea: Add new options for "fail immediately" and "default success state"

Repro steps:

1. Launch app with Wanikani API enabled

2. Click 'Start' while API is still loading

On rare occasions this causes a crash