I can see how many total lessons I have. Granted it is a user script, one of the few that I do use. It is a feature that I personally believe should be standard, but that is just my opinion. I do appreciate that I have the option to add it. Not a deal breaker, but nice to have.
Iād be overjoyed if they just announced major breaking changes to script authors on the forum a day or two before and pushed them to the preview site - Iām definitely not asking them to halt their āinnovationā for scripts
My biggest issue is their lack of advance communication and their lack of clarity on breaking a major part of the public APIā¦
Could not agree more. I would only say that it should be more than a day or two notice. If I was responsible for product management I would set up a system/process whereby any script author that desires to can register with us and then maintain an email distribution list for such occasions.
There is a mailing list, link at the bottom of the sidebar in the api doc: https://docs.api.wanikani.com/20170710
The question is, however, is it still active?
Very good to see that it was thought of and they have it. Hopefully it is being used for the stated purpose and hopefully script devs/maintainers are registering for it.
Sadly I donāt even remember the last time I received an email from that API mailing list - definitely not for todayās changesā¦
Sorry but hard disagree on this one.
Forcing a decision unto the user is bad practice and should be avoided. Allowing users to be the sole decision is good, and thus this feature should be added.
I just want to correct this āFake Newsā. The development team is larger than just me.
Sorry - I should have specified that I meant devs working on the code specifically, I know thereās many more people working on the content side etc. And obviously I may be totally wrong on that still, I was simply basing that off of not seeing any other devs posting on the forum
We have 3 full-time devs working on code, lots goes on behind the scenes and the forum isnāt always a friendly place so it isnāt for everyone
Thatā¦ kind of proves my point. If you want somethingāor donāt want it, as the case may beāyou need a script, one for which thereās no guarantee it wonāt break for potentially several days if not longer the next time WK changes something, because WK aināt gonna give you the choice.
So they have to provide every feature any user might want (which can be turned on or off)? Thatās not feasible and not good practice IMO.
Hard disagree.
You obviously missed the point of what was said so Iād just advise you move on.
I am 100% on board. This site is not a good experience for me without a few add-ons. The double-check script is the most crucial one. I donāt care how much Tofugu or anyone else thinks this script is problematic, because we, as paying users, donāt need a nanny telling us how to learn. If I make a careless mistake or typo, it shouldnāt set me back a month or two of SRS. If you donāt want to have this feature, thatās entirely understandable, but for me, itās critical.
This service has no rankings or competitive rewards. This is a personal, individual service, and we as users should be afforded the option of using whatever common tools and techniques work best for us, to reach the goals weāve set for ourselves.
The popularity and widespread use of scripts highlights that there is a strong desire for this. There are gaps in the app functionality that make it a poor experience for many users. Adding the option of enabling the most popular of these, as implemented an maintained by Tofugu, is a strong requirement, IMO.
I view WaniKani as a finished product (even though I know it isnāt since there is still work done).
I pay my subscription to get exactly what āVanilla WaniKaniā has to offer. I am happy that I am able to use User Scripts but thatās a plus for me, not something I expect to be included in the service I am buying with my subscription.
I think its valid to wish for functions to be added but think its weird to have that hard feelings about it if it doesnāt happen.
- Your desire to force people into a particular way of learning, whether they like it or not, is not a good argument for not having the option available.
- Most of these features would be relatively easy to implement with access to the source code. Iāve been a front-end developer for 16 years, and the majority of the most useful scripts would be easy, or even trivial to develop and maintain with full source code access.
- As a paying user, Iām not asking WaniKani to entitle me to third party tools. I asking them to implement the functionality of some of the most popular third party tools themselves, making them first-party.
Itās not weird at all. The core of the product is good, but the app functionality has large holes that were filled by user-developed scripts. Being upset when those scripts break, due to WaniKani developers refactoring and improving the codebase, is indeed weird. Rather, Iām upset that they havenāt added many of the features that these scripts provide themselves.
But where does the expectation to these scripts come from?
In the first 3 free levels you were able to see exactly what WaniKani has to offer and you decided to get a subscription. No one forced anyone to subscribe.
The expectation is derived from a fundamental desire that any community should have to improve the experience of its users, especially in cases where there are clear paths to do so.
Saying that we arenāt āforced to subscribeā is a meaningless argument. The fact that subscriptions are voluntary doesnāt mean that the value provided by them needs to be static. After all, a subscription is usually a recurring cost, and nearly all successful subscription services change and improve (or at least try to).