You and me both would much prefer this. I’ve made an exception to my rule to get this script though, I just consider the summary page an important part of the experience.
2 Likes
Hey look this thread is active once more
Anyway
MaruMori
5 Likes
I think they intended to make the Review page, each items, load faster; but in my experience, they actually loaded slower for the first few weeks. It might be a little faster now, fast enough not to see problems on my side. (Old code is already fast enough, though.)
There remain problems with audio being slow. Actually, a new problem.
But certainly, the development team absolutely doesn’t work faster. Pretty much every suggestions about the code fix and UI are ignored.
On the other side, contents are being updated, like more Kanji and vocabularies and more synonyms.
5 Likes
To be honest, I thought the summary page being taken away would be one of those things that I would eventually get used to and it would quit bothering me because it wasn’t important as I thought it was. Or that they would bring it back after a few weeks.
Well, it’s been half a year and I’m still irritated they got rid of it. After a big bunch of reviews it was helpful to see which ones I had gotten correct and which ones I had gotten wrong, and which level they went up or down to all together. You can criticize “gamification” if you want, but it is motivating and is a good way to easily judge how you’re doing. The “recent mistakes” board is not the same with that big wall of blocks (that aren’t totaled), and I don’t really understand the criteria it’s sorted by anyway.
I don’t use userscripts but I might start adding some.
17 Likes
Content team has always remained diligent which is good to see. Do love how open to feedback and suggestions they are :).
7 Likes
Oh yeah it’s just with summary page and kana opt-out that they have taken a stance of utter silence
3 Likes
It’s only been 19 days, give’em a chance
12 Likes
wasn’t it supposed to be in Feb next year sometime, えとー
えとー the 30th was it? 
1 Like
Not sure if you have an android device, but my app Hakubun has a summary page that may help. iOS release is upcoming!
2 Likes
I do have an android device, though I’ve been using Flaming Durtles when I want to study on my phone. I know there’s that new “smoldering durtles” app that does the same thing too, never heard of Hakubun.
I only do a little bit of reviews on my phone though, I much prefer to do reviews on my computer, since I write so much faster there.
I usually read articles on NHKeasynews when I wanna study on my phone.
1 Like
Good to know! Yeah, Hakubun is still in alpha so it’s a work in progress. It’s actually a hybrid app though, so I’m gonna release a web/desktop version of it once I make sure everything is responsive enough since I know a lot of people prefer studying on their computers. I really loved the reading practice on Jakeipuu (abandoned WaniKani app, but that part actually still works) and want to add something similar eventually.
Screenshot is reading practice from Jakeipuu, not my app
4 Likes
I´ve not been around as much because I got fucked over by my workschedule and had to drop japanese entirely for several weeks. I tried to keep up with WK but it´s state makes it very difficult to use.
It has now been over 6 1/2 months with absolutely nothing. This is the biggest fuck you I have ever received for paying for a product. I predicted months ago that this is how the team would play it, ignore it and wait for the people to get used to the worse experience until the userbase is mostly switched out for people that never knew what we lost. But to actually see it makes me incredibly upset and sadly it seems to be working too. The amount of people complaining has gone down significantly, which might also have to do with the fact that everybody starts to get used to the fact that the development team just doesn´t care.
@Mods This is probably futile, as people have done this in the past (including me), but can you give us at least something? At least tell the people that we won´t get the page back, that we will never get a Kana-Opt-Out, that you will never re-open the Review-API and so on. But telling us that you are “working on it” and then going radio-silent for over half a year is completely unacceptable.
You may have been able to hide behind the excuse of updating the codebase to “enable faster changes” but we have now all seen this was a lie.
If there are any roadblocks that keep you from making progress then tell us that, but tell us what´s going on and don´t leave us hanging.
27 Likes
So to play dev’s advocate here, one game plan when trying to defend under-the-covers refactoring to a nontechnical audience, is to say that you’re investing in future development, that the work you’re doing now will make it easier to do work later. The problem is that the later work is outside the hands of the developers doing that maintenance work, so while theoretically this should make future feature development easier, none of that matters if your contract doesn’t get renewed.
I think what TofuguScott and team were working on was migrating Wanikani to a cloud-native architecture, which probably cuts down a lot on server costs and makes deployments way easier. The problem with this is that tracking user sessions is a nightmare with the requirements of cloud architecture, and combined with a few other requirements they weren’t willing to compromise on, like being able to jump between devices, made the problem intractable.
The user scripts work by keeping track of your session on your browser, which only works if you do all your reviews on a single device. Works great for me, but since jumping between desktop and mobile was a major priority in the redesign, it doesn’t gel well with those goals. Basically, I think they made the wrong choice at a basic architectural level, and now we’re all stuck with it.
4 Likes
FWIW, I buy much if not all of this, but think it remains to be seen if their architectural choices are wrong for the majority of Wanikani users (current and potential).
Scripts and APIs are nice for power users. The summary page was nice for some fraction of users, too. It’s unclear to me what fraction of the current and potential user base these fractions comprise (especially since many scripts are unaffected). It’s also unclear to me if potential solutions or even advancements are possible with the current architecture. (Tbf, I never paid any attention to the summary page and haven’t done a review in months.)
Personally, I care a whole lot more about the content than any of this. Whatever complaints we might have about the delivery, they’ve clearly hired well and paid a lot of attention to content.
The main complaint I’m aware of with content of was introducing too much kana-only vocabulary (primarily a temporary concern/annoyance to advanced users who were approaching the end of their lessons — a small fraction of users for sure). They’ve clearly paid attention to user requests regarding context sentences, parts of speech, etc.
With respect to delivery, many of us did the bulk of our sessions on one device (myself included). Is it reasonable to assume the majority of future users will do the same? The prior review API architecture risked ruining the experience for all users — was their decision to make it return empty results vs. crashing scripts wrong?
My answer to both is honestly “I don’t know”.
This all pales in comparison to breaking architectural changes in Windows or OS X history, for example.
And it seems nothing is forever with software. Despite the long delay, I still wouldn’t be surprised to see the concept of sessions return at some point, possibly in an unexpected form.
7 Likes
Underappreciated play of the year.
4 Likes
That I agree with, the latest additions (contentious kana vocab notwithstanding) have been very good IMO.
MaruMoriii
4 Likes
so… I guess this is never coming back and we are playing the ‘ignore and forget’ card
11 Likes
I think at this point it’s fair to assume that the new “Recent mistakes” widget is what they intended as a replacement, for better or worse.
Or maybe not, after all they also said they would add a kana vocab toggle and it’s nowhere to be found (although admittedly they also haven’t added any new kana vocab since, so maybe they’re reworking the entire concept).
6 Likes
So keeping this post at the top may be a way to conter this?
We still do remember.
3 Likes