No, I hadn’t considered it. I can’t think of any reason why it wouldn’t be possible. Probably easiest to have a config setting where you could specify a link to an external .js file rather than copy/paste the script into a text field. But, as always, the issue is finding the time to do it.
Always open to contributions. Did you have something specific in mind? Feel free to mail me.
I see the ultimate reorder is already a high priority if I understood correctly, yay! =D
If all features of it is somewhat hard, how about only the separating of type? (Radical/Kanji/Vocab)
So we can easily just choose to do radicals first, kanji next and vocab last both on lessons and reviews. So if I level up while away from the computer I get to start of the radicals without having to press through all new vocabs first (that unlocked from guruing kanji, thus belong to previous level and comes first). I feel I learn better by doing smaller amounts at a time, and there are more than enough time to finish all vocabs while waiting for the reviews of the radicals to guru, and second part I finish the new vocabs before the second half of kanji guru; getting a zero on lessons minimum twice per level (and I do all reviews all the time, keeping it at zero as much as possible) =)
So lessons is a bigger priority for me than reviews, but both is loved =)
Yes. 3.0 (currently in beta) will have support for iPhone X. I don’t have a release timeline for 3.0 yet, as I’m waiting for the WaniKani API v2 to be released first.
I have a list of 5 or 6 user scripts that have been requested over the years that I’d like to add to the app, and katakana madness is one of them. Some of these scripts will make it into 3.0, depending on how long it takes the v2 API to be released. Beyond that, I don’t want to make any more specific a commitment as I don’t want to get anyone’s hopes up.
I doubt that that would work reliable enough to be worth it. But yes, typing on mobile is so annoying. I wish there was a way to use the WaniKani Anki script (modified version for mobile, including buttons) on iOS. I was even considering forking one of the existing apps and building my own just so that I could include the Anki script (but didn’t seem worth the effort).
Currently, I have to use a crappy Android device to do my reviews because you can’t install userscripts on iOS. If the Anki script was ever included in AlliCrab, I would be sooo happy
I suggested at one point just allowing a text input or URL reference (full disclosure, I think that was @cplaverty’s suggestion in response to mine) for custom scripts on AlliCrab. @cplaverty are you still considering doing that?
A problem turned up today: the review count doesn‘t go below 17. I did my 17 reviews this morning, they went through (on the dashboard everything is normal), but the app wouldn‘t update. Lesson count updated correctly. When I try updating by pulling down, I get ‘Failed to update data’ ‘Data couldn‘t be read because it is missing’. When new reviews turn up, the red number icon notifying me says 17+number of new reviews, while inside the app, it stays 17. Any help?
Edit: eeks. I tried signing out and signing in again, now it doesn‘t display any numbers and still gives me same error message.
Edit2: it says it updated „just now“, but it doesn‘t display anything anymore. No review or lesson count, timeline, items, everythings gone. Help? Please?
Edit3: it‘s just the beta testing version. The normal one works as it should.
@cplaverty For a while now the app (regular version, not beta) has been crashing the first time I try to open the app. This occurs on iPhone 8, latest iOS. It always opens on the second attempt, so it’s not a big deal, but I wanted to let you know.
Disclaimer: I’m not supporting this fix in any way, I just use the app everyday and so it not working properly was starting to hamper my WaniKani rhythm, so I got a bit desperate to make a quick fix. I’m sure Chris’ll sort out a proper fix for it later.
Hi folks! Apologies for not replying here sooner, but it’s been a busy couple months.
As has been noted, the current beta is broken due to a recent breaking change in the API v2. @onimitch has kindly submitted a fix for this. I’m going to make another tweak or two due to other non-breaking changes in the API, after which I’ll get a new beta out.