Just a quick update. As part of the work to remove legacy code from Wanikani, we have updated the SRS counts that show up on the dashboard and profiles pages. The new view now shows the breakdown for each SRS stage without the need for user interaction which improves the user experience and general accessibility.
That’s a brilliant change. The joke is I had no idea I could hover and see the breakdown until a few weeks ago when someone mentioned it on the thread… so making it a visible feature instead of a hidden one may help other user too, so thanks for that.
Still waiting for an undo and a skip button so I won’t have to use a third party app for it.
12 Likes
I wonder if it’s possible to see substages, like the [Userscript] WaniKani Dashboard SRS and Leech Breakdown addon. That’s more useful for workload planning the raw types.
2 Likes
I love this change! Great job!
2 Likes
Just saw and I thought i was tripping for a second lol
3 Likes
I don’t think I knew there was more information hidden in there either. If I did I forgot a long time ago, even though I look at those numbers every single day several times.
5 Likes
I hardly ever see it since it was pushed down by all the new features, I wish it was under the header so I’ll get this info the moment I load the dashboard, it makes more sense to me that way.
1 Like
Another change without any options for those that dont need or want it.
Is it really so hard to have a “Dont show breakdown” option?
The old one was out of the way and understated.
Now its in your face like a checkerboard pattern as you scroll past it.
Why would i constantly need to know how many of each item is in each tier
if i cant do anything about it anyway?
The only number i care about, the Apprentice count, is now smaller and harder to see at a glance, which makes my user experience worse.
3 Likes
I love this change! 
1 Like
Nice change! Looks nicer, cleaner, and more straightforward than the old layout I think. And just looks kinda pretty in general. I like it.
3 Likes
Definitely not!
Adding options and configuration is trivial!
You and others might prefer Anki.
1 Like
Those two things are not mutually exclusive.
4 Likes
I like the change, but I’m not in love with the white backgrounds.
5 Likes
Not for me. The old version had nicer design, showed only the overall count, and was much clearer for reading. Now there are huge white boxes all over the place, and I don’t need to know how many of those items are radicals or kanji.
If WK wants to make better user experience, how about you split it by level? It would be much more useful to know how many items are in apprentice 1/2/3/4 and guru 1/2 than to split it by type.
…and this change broke 3 scripts that I was using. I managed to fix 2, no idea how to get the third one working, so “thanks”. For reference, this is what it looked like before you broke it - it was pretty, full of useful informations, and easy to read:
Edit: I managed to scamble something out of it:
7 Likes
Uuuuuh, that’s nice!
1 Like
Looks great!
Oh, that’s looking nice, great job there!
I do wonder however, if a darker version of the colours would look nicer instead of the white boxes.
3 Likes
@tofugu-scott It would be really great to see a recent mistakes burn items section be made.
There’s really no need to be so dismissive and aggressive for a small change that at worse increases information density a minuscule amount and does not remove anything. I’ve got my gripes with the WaniKani software but how can we expect them to improve if every time they make a minuscule change we jump at their throats because it’s never good enough?
Meanwhile bring the bloody review API back damnit, or at least give me basic review stats directly on the website.
5 Likes
Wholeheartedly agree with this. Even if you absolutely despise this change, it’s not one that can’t be worked around with one second of effort - and therefor absolutely not worth complaining about. Complaining about trivial changes like this takes away the meaning behind the actually valid complaints regarding other things - like font changes, lesson changes, and especially the Reviews API endpoint being disabled. There are plenty of things to complain about on WaniKani, and the surface-level appearance of a single UI element that you have to scroll down 2 full pages just to see is not worth complaining about no matter how much you hate it.
That being said, for the love of god please turn back on the Reviews API endpoint. We’ve been waiting for that for over a year now and there’s literally zero benefit to keeping it disabled. It is not a personal preference - it is an outright negative by every metric. In the time you spent redesigning a UI element that nobody uses you could have fixed an API endpoint that 1/3 of your userbase misses dearly.
4 Likes