Please bring back the summary

For a study app, WK must be without a doubt in my top 5, maybe 3 apps time spent-wise ever. Also, I’m planning to get to level 60 and potentially burn all items during this and the following year. The study timing fits my needs and it’s overall a well-thought organization in how kanji and vocabulary are taught.

Obviously, I love WK more than I hate it but dude, what in the world are you thinking about?

As many others are constantly reminding you, these changes shouldn’t have been made in such a rush or without enough feedback from the user base. This was simply put a bad move

I’m surprised that user-scripts needed to “patch” what you took away and the existing ones that crashed were made and updated in a matter of days, and you’re here still brainstorming on how to somehow implement changes.

Forgive me if I sound here way too rude but this is an “insert_generic_response.txt” Listen, this discourages me more than it helps. Because based solely on the wording you use,

to me, it reads like, “we haven’t even thought about a decent solution… more than two weeks later”

Meaning you didn’t think about a solution when the update launched, because you thought timeouts were way more important than the summary page. At least myself I couldn’t care less about timeouts and do miss a lot the summary page and more than everything I miss WK having memory of the sessions

It actually got worse for my own experience as I tried to express in the main update topic: I do reviews on the subway, connection issues happen 4-5 times while commuting and I have to restart the review sessions, wk loses memory of my progress so I have to redo sometimes more than 20 items again (per disconnect), and to be honest with myself I have to fail them in purpose if I had failed them before the network issue.

Before, if i already answered the meaning, i would only be asked about the reading. Now I’ll have to do both again. If my review batch is over 200 items, that means that I don’t always remember if I just failed the specific item because I’m suddenly in a rush to finish on time because i suddenly have to reanswer 50+ items because of the constant network issues.

NICK, IT IS ANNOYING

It also makes it hard for me to believe that you’re really working on adding features that have been asked for a very long time if you never thought about this one thoroughly.

Sighs

17 Likes

For the network issues, I can recommend the Juken app. If the network call fails for some reason, the app will cache the result and re-try it when connectivity is back. Downside is of course that the app replaces the type-in quiz with a simple self-evaluated flash card quiz, so if that’s important to you then it’s not an option.

But regarding the summary page, I think what annoys me most is WK’s silence about how they intend to solve this. It’s been weeks and the backlash has been substantial. I know it’s impacting my kanji learning negatively, and as a paying customer since 2016 (welp :cold_sweat:), I think I have a right to voice my dissatisfaction. To limit the damage done here, WK will really need to step up their communication game like yesterday! What are you doing, what concepts have you come up with, and what’s the timeline for implementation?

8 Likes

:arrow_up: This. Seriously.

11 Likes

Thank you for the kind suggestion. I’ll have to take a look at it. For now I’ve been using flaming durtles and I’m not sure if it put things in cache but it has been a better experience so far.

Agreed. I think that it’s really important that we keep pushing. Regardless of the silence, the seeming lack of care from WK team and the lack of empathy from other users that don’t find issues at all in these changes.

I’ve been “here” since 2018, so I’ve also seen a lot of changes. Generally speaking, they are content related or minor UI changes that although caused some reaction, (like the radical overhaul). They were either duly notified or had a solid reasoning behind them.

Either way, content related changes have always had the flexibility to allow users to, for example, use their own synonyms or adding their own notes.

Other changes like the extra study section or the review timeline were additions, you can like them or not, you can use them or not but they do not substract from the experience of using the app

This time is different. WK is all about lessons and SRS reviews. You take a lesson once and then if everything goes smoothly you will only review an item 8 times. (We know that’s rarely the case).

For something so inherently relevant as reviews and lessons. Taking away (or changing if you will)one of the main driving characteristics that determines how things work and that has been around so long that a broad extension of your users have get used to it and have grown with it it’s something that should be notified with time and exposure.

Something that changes the core of your app functionality is something that has to be carefully looked into because (as we’ve all noticed) is something that can substract rather than add.

Then they sell it as a regular change or feature.
Then they make a thread where wholeheartedly ignored every single complaint against the change and only focused in trying to help people with issues with the new version
Then they explain that going back is not possible
Then they keep looking away for almost a month now from all the threads complaining, answering at most an “oh yes we’re brainstorming it”
And as you beautifully pointed out, they simply made the choice of not opening a communication channel from where we could have a conversation about this.

Who decided these, who approved it and why this is all happening is beyond me.

As always, we look for help from third party scripts and apps. Thank you all that have contributed to make this app and community so brutally useful and enriching.

Well, let’s see how this keeps evolving as we continue to voice our concerns

9 Likes

The removal of summary page was the dumbest update ever. At this point I’d rather have the timeout and summary page back if that’s what it takes to be honest.

13 Likes

@WaniConti (or @TofuguJenny) can we please get an update here? Is the team actively working on restoring this really sorely missed functionality? Is there some sort of timeline when we can look forward to again enjoying our review and lesson summaries?

Just to reiterate, the summary really is/was an important learning tool. We’re all here to learn kanji in the most efficient way possible, and with the summary removal you have degraded the quality of the site, and the efficiency of our learning process. This is kind of a big deal, and one I’m not willing to simply accept. I’m sorry if I seem vocal and/or stubborn, but the WaniKani kanji learning voyage is important to me, I’ve already invested huge amounts of time (and not insignificant financial value as well), and I really would like you to to listen to your customer base here.

17 Likes

Its the year 2023 and this program doesn’t even have a dark mode option…(Even though this forum does?)

And although I am relatively new, everything I have read seems to point that they only add or remove features if they want to. No amount of “outcry” here on the forums matter, unless it has to do with incorrect word usage or something. I think they look at raw numbers like subscriptions and such, and judge performance from there.

I have seen countless threads regarding the summery page. Many of them closed by the admin. The only options are to either use a phone App, or use kamesame, which I actually think I am going to be switching to as a replacement around level 15. But even that doesn’t offer dark mode. Its always something.

4 Likes

It is actually quite infuriating to read these generic responses from the WK team. Looking at how much time has passed, and that since the “update” (more like a “downdate” imho) new fixes have been introduced regarding typos, it is surely coming through as if they don’t give a flying f about their user’s feedback. The minimum effort I would expect is a pinned topic constantly updated about their progress on the summary page and an apology for messing up people’s study routine. An amazing user fixed their mistake in a couple days, and WK team is expecting me to believe that in weeks they did nothing? While it is their job? Laughable.

I am deeply disappointed in this team.

15 Likes

Its not that they cant* fix it, its that they wont. They aren’t completely incompetent. They have a personal vision of the product… And the attitude is simply if you don’t like it, leave.

5 Likes

Exactly. Nothing wrong with having a personal vision for a product - everything wrong, with pushing that vision through your paying user base with force, regardless of their response to your vision.

4 Likes

Just store summary items in the localStorage as a substitute of a server session.

  1. User hits Review button → create a new session store in the localStorage
  2. As the review goes, store correct/incorrect items in localStorage
  3. Review queue goes to zero → display stuff from localStorage (summary page) and after that clear it out

It’s that simple. Only downside is that session data is now per-browser, but that’s fine I guess.

Edit: Guess I should tag @tofugu-scott here, lol. Also, localStorage is persisted even when you close the browser.

6 Likes

I already made the same suggestion, but server-side instead of client-side. The problem is clearly solvable, don’t know what’s so complicated about it.

3 Likes

image

5 Likes

More than a month has gone by since I posted my request to bring the summary and we still don’t have any concrete response about fixing this major WaniKani downgrade. Each time I’m reviewing I feel a mix of sadness an anger knowing that there won’t be a summary at the end of the review.
Over the many years I have been using WaniKani, that summary, specially the percentage I got right, had always been my way of getting immediate feedback about my performance after each review session. I really miss it.

17 Likes

I still really miss it. There was a userscript I was using but tofugo has restricted access to the review table so that no longer works. This was because accessing the review table for a review summary was slowing down reviews. We know they removed the “session” but this must have been an index. If you are trying to access reviews by time you probably need an index on the time field and this is probably missing. If I am right I don’t think this is something to add without thinking about it as adding extra indexes can affect performance.
I really hope they come up with an alternative soon.

4 Likes

Same here. Especially when you do a big batch of reviews and get absolutely no feedback at the end is so frustrating.

I’m so disappointed in the wanikani team going completely silent on this topic and showing no interest whatsoever in fixing this.

9 Likes

I hope as much as you that WK will do right to its users and bring the summary back.

In the meantime there are userscripts solutions (with also the percentage you want)
Userscript wanikani heatmpap
Userscript-review-summary-on-the-dashboard

I do not endorse WK in relying long term on the unpaid work of users for essential features, but I prefer to remain positive they will do something about this soon. (If you are reading this, please)

@cforbes @Doggo8 They do work now, You might need to update them to the latest version in tampermonkey

1 Like

the heatmap is not what I want. I want to see specific errors.
I tried updating the review summary userscript and it still doesn’t work.

I’m just slowing down reviews and using the review page when I get something wrong to look up things like similar kanji as I go. I just have to stop automatically hitting enter.

1 Like

Then, the solution is probably both server side and client side. Server side for heatmap, client side for session summary.

It’s ok to try to reduce the server load, but no warning regarding the API will-change is bad. Then, a proposed alternative is in another thread, but the API is already brought down before any fix, temporary or not.

2 Likes

Grab the newest version of the script. They’ve updated it to use the supported API, and now it’s lightning quick.

1 Like