Hey everyone,
I’d like to hear how others feel about WaniKani’s direction and how feedback is handled. I’m a lifetime member, I’ve referred many friends and I’m always singing its praises. I appreciate Tofugu’s work helping us learn Japanese. A few things have frustrated me, though, and I’d welcome their perspective.
I develop Wanilog, which thousands of WaniKani learners use, so I have a personal stake.
For some of us, WK Stats, Tsurukame, Kakehashi, Smouldering Durtles, Double-Check, Ultimate Timeline, Item Inspector, and Jitai are part of everyday study. Apologies to anyone I’ve missed!
This work is unpaid: devs build features, answer support questions and fix things in their spare time. It adds value to a paid service, yet I sometimes feel underappreciated when discussions focus on restrictions. I’d like more of a conversation about how we can work together.
I understand that third-party apps and userscripts are unofficial and unsupported, and that the team can’t guarantee compatibility with every update. Keeping them working is our responsibility as developers. Advance notice and clear technical notes would still help us do that work.
Shortly after I added lessons and reviews to Wanilog, staff contacted me about API guidelines they were already revising and suggested pausing further updates. The branding changes would affect other apps too. I clarified Wanilog’s unofficial status as requested. I don’t know when those changes were first planned, but being asked to pause just as I’d expanded the app felt discouraging and left me unsure how to plan further development.
With the recent item-info change, related items began opening within reviews instead of new tabs. Scott restored proper links and Ctrl/Cmd-click support, which I appreciate, but users still reported difficulty navigating back through items. I shared Wanilog’s option to use new tabs or a closable modal. Staff asked me to keep Wanilog posts in its dedicated thread, and my reply was hidden. I understand limiting promotion, but this was discouraging while the remaining navigation problem had no clear answer. Could there be room for disclosed, relevant workarounds?
There have been similar conversations before. In July 2024, the dashboard update broke established scripts. The broader migration had been announced, but that release had no advance notice or preview testing. Hubbit200 asked for clearer warnings and progress updates while acknowledging the team’s difficulties.
Individual review history API access was disabled in April 2023 because of performance problems. Users were still asking for updates in March 2025. That October, staff confirmed individual review data was no longer stored. Statistics tools lost a capability they relied on; official dashboard widgets don’t restore developers’ access.
I appreciate improvements such as the lesson picker, customisable dashboard and review-ordering options. Recent Mistakes and Last Answers also restored some lost summary functionality. I’d like that progress to come with clearer answers about what remains unresolved.
Could we have:
- A visible outcome when feedback gets “passed along”, including why a request is declined?
- Advance notice and technical notes for changes likely to break tools, with a preview where possible?
- A clearer explanation of how community developers fit into WaniKani’s future, and what support the team can offer?
I’m sharing this discussion with Wanilog users so they can contribute their own experiences.
Am I the only one finding this frustrating? If you’ve reported a problem or suggested a change and felt it went nowhere, I’d like to hear what happened and what would have helped. And if you’ve had a better experience, I’d like to hear that too ![]()