DISCLAIMER: THIS ISN’T YET ANOTHER THREAD ABOUT HOW EARLY LEVELS ARE TOO SLOW.
In fact, the current proposal may make levels even slower.
MAIN PROPOSAL: Based on success rate of user during reviews, adjust the number of radicals they will see on the next level, from x0.25 to x2.0.
- In the case of smaller amount of radicals, additional “intermediate” levels are created: once you have guru’d all your allocated radicals, plus 90% of the appropriate ratio of kanjis (same rate as the radicals or of all available kanjis for the unlocked radicals, whichever is lower), you unlock the extra radicals for that level (and additional available kanjis, if applicable)
- In the case of larger amount of radicals, the number of kanji/vocab per level does NOT change. The only difference is that some levels may go from being ~7days levels to being ~3.5 days levels.
ALTERNATIVE PROPOSAL: Same as the main proposal, but the rate is adjustable in the danger zone rather than based on an algorithm. It seems easier to program.
- WaniKani has very nice dependency tree going radicals -> kanji -> vocab.
- Number of radical per level seems “fair”, but is arbitrary in grand scheme of things
- This proposal is inspired by this discussion between @koichi and @Vanilla about how to reward fast (correct) reviews. Note that it also applies to the case where the user is making a lot of mistakes.
EXPECTED RESULT: People will get a more appropriate review queue size. Those who are having troubles keeping up will get a lower amount of lessons without having to self-regulate. Those who find things are too slow (and are breezing through their reviews) will get more lessons, but in a controlled way, so that they don’t risk to be overwelhmed later on. (Also, in the algorithmic case, that will also be taken into account, plus resetting a few levels back is always an option too if things really get out of hands)
ADDITIONAL COMMENT: I feel it wouldn’t be to much of a hassle to code, since there’s already an order for radicals and a full dependency tree. If I understand correctly, there’s a (major?) update of WK coming, so I thought it’s the right timing to make that suggestion.