Can you add a button for hiding known grammar on the Path book pages?
@Pushindawood I know it must sound like I’m nagging by now, but do you ever plan to update your version of wanakana? There’s a bug in the version you’re using where typing in the middle of a word sends the cursor to the end on conversion. This makes it painful to use when fixing typos. This bug has been fixed for well over a year now in wanakana.
3 Likes
While audio is nice, it is not necessary for every sentence. I would rather see more content than audio for every sentence (just my preference).
Regarding the space where you input your answer, I hate how “casual” or “formal” disappear as I am typing. Seems silly, but sometimes I just forget which form it should be in.
8 Likes
I second this, as well an kanji input support.
1 Like
I would like this feature, because the “troubled grammar” feature does not target my weak points at all, and with your recommendation I could at least choose.
1 Like
Sorry if this has been suggested before, but would be nice to have the option to review stamped 
sentences again in a reverse platform, such as a simple flashcard of the Japanese sentences (separate from the main platform like ‘Cram’). I hesitate to suggest a reverse-productive input as this would likely be a nightmare to architect so I’m just suggesting comprehensive reading akin to a classic SRS style or just a simple flashcard. Seems we wave さようなら forever to all these excellent example sentences after ‘ing’ but would be nice to check later on that I can still comprehend the Japanese meanings if I haven’t seen it in a while.
4 Likes
Under がする this post would be very useful to add to the readings:
To explain why がする is used as opposed to say 聞こえる.
2 Likes
Settings for JLPT level: please add an “auto” entry to the list of the JLPT levels to study. Every time you add grammar into N5 - N3 users on N2 need to manually change the JLPT level setting in order to study the new grammar points. That’s not very comfortable.
“Auto” would just add the latest grammar from the lowest levels automatically into the study mode.
6 Likes
Shouldn’t sentences for this grammar point have the suggestion of のような as alternative grammar and vice versa?
In case you didn’t see it @Johnathan-Weir , we’ve had some discussions that may be helpful. Some nuances don’t apply regarding みたいな・のように interchanging.
Nothing I haven’t really found before. As far as I can tell from lots of googling they are almost always interchangeable except for a few set phrases (このように, etc). The vast majority of answers just say よう is just more formal than みたい.
It would just be helpful if they said whether or not they’re interchangeable on a per sentence basis.
1 Like
Discussion section could just be another tab after ‘readings’
2 Likes
You know that post is over a year old, right? There is already a discussion section on these forums in the #grammar-points section.
new to these forums and didn’t realize until after I posted, no need to be rude.
2 Likes
Grammar point suggestion: または - “or, otherwise”
I always mistake または and またも so would be nice to have a grammar point for that.
3 Likes
@dakotalightsmith
Hey and welcome on community forums 
@Anthropos888
I have added it to the (very long) to-do list!
I am surprised though that we do not have it covered already 
6 Likes
Since we’ve started expanding on the nuances that can fit into the answer blanks during reviews, I’ve started to think that there may be a need to clarify everything that’s been marked as “casual:”
If the grammar itself is restricted to casual settings, the tag should be [casual]
If a review wants 辞書形 (not ですます体 or 敬語), the tag should be [casual form]
Then, for consistency’s sake, IIRC there are reviews marked with [polite] (asking for ですます体) that should then be changed to [polite form] to match.
The good news is, I don’t believe that any grammar points themselves are marked as [polite] (because they are marked with [formal] instead), so at least that change should be easy/straightforward to make all at once.
In the instance that a review wants 辞書形 on a casual grammar point, I think [casual] works as a catchall (so, no need for [casual・casual form], which looks a bit redundant, but maybe that explicitness would be good anyway).
Alternatively, instead of [casual form] maybe we could use [辞書形] or [dictionary form], and then [ですます体] for polite verb forms.
I’m also starting to think it might be nice to have an option to toggle kanji on/off (probably defaulted to “off”) in the answer blanks; I personally like any excuse for more kanji exposure, but kanji hints won’t be very useful (and likely frustrating) to anyone who can’t read them yet.
7 Likes
That would be helpful. I would prefer these four nuance hints:
Casual grammar
Formal grammar
Casual form
Polite form
4 Likes
This has probably been said but,
-JLPT
-Automatic audio for the review cards!!
What about the JLPT?