Hey dont know whether itās my phones problem or the apps. Just thought I might ask of anybody knows a solution. Since recently I am no lomger able to use the app to go to the forums and stuff. The load bar loads and then the screen goes blank. Reviews and learning works as usual.
Any guesses what happened?
This is a really good app. Saves time from opening the website. Also provides notifications in case I forget.
Not sure if itās my phone or not, but the app seems to be having trouble connecting through mobile network (works fine on WiFi) - any idea why this might be happening?
I dont know if this is the right place⦠But i use the wanikani Android app a lot as its way more flexible.
So i was wondering if it would be possible to incorporate the learning reorder script into the app. I would like to learn the radicals and Kanji first and then do vocabs over the period it takes to level but I currently donāt have a computer so I have to go through mountains of vocab before reaching the radicals and kanji.
just make sure you get to 0/0 before guruing your last kanji for the level ā then youāll always get radicals and kanji first
If you have an android phone, the reorder script works on Firefox
does the ignore script also work? Asking for a friend.
A good advice regardless of whether you use a phone or a computer
The override script works, which provides the same feature I think
On the settings page on the wanikani site itself, you can stop the audio from autoplaying during reviews and lessons. If you change these settings, itāll mute on the app as well
This app is great. Iām faster on a PC but I use it all the time when Iām away from the computer.
I just wanted to suggest a dark mode if possible? I just found Breeze for the web version and my eyes are very happy about it. Not sure if this app is in any form of active development but itās just a thought.
Looks like this app is no longer available on the Google Play store ā unless Iām looking in the wrong place ⦠?
It was no longer maintained anyway. There is another application, Flaming Durtles, that works like a charm.
Love this app. Still use it to this day and vastly prefer it over Flying Durtles. Canāt really say why, it has less features, but it just āfeelsā right with all the little things that I miss when using Flaming Durtles. Saddens me that it will be dead once API v1 will be discontinued.
Anyone with coding knowledge has any idea how feasible/difficult it is to make it work with API v2?
Itās definitely feasible, and not too difficult for someone with experience in native Android app development. But itād be a lot of work, Iād guess a few solid days of coding. All in all, the biggest problem would be to find a developer who has the right skills and experience, and who would be willing to dive into an old, dusty piece of code like that. Especially since it would probably also be a big, unpleasant job to polish the code to a state where itās acceptable for the Play Store again. Google has a lot of rules for that.
Itās all possible in theory, but I fear all of the old Android apps will simply die a quiet death come September.
the biggest problem would be to find a developer who has the right skills and experience, and who would be willing to dive into an old, dusty piece of code like that. Especially since it would probably also be a big, unpleasant job to polish the code
Yeeep. I doubt anyone would be willing to deal with this codebase unless paid properly.
Thatās also why I think trying to upgrade this codebase to API v2 isnāt a great idea. Youāll have to change plenty of things and thatāll inevitably be a pain. When I say the codebase is a time machine on GitHub, I mean it - quite a bit in there is straight from 2013.
Now, regarding working on a new app, Iāve thought about it a few times. Even started some work. But then ādonāt even remember whereā I read rumors of official apps being in development, so I figured maybe I shouldnāt bother. Add to that my free time decreasing and the project died.
Itās been around a year since then, and thereās still no official apps in horizon, so maybe whoever wrote what I read was mistaken and after all, maybe itās a decent idea to build a new app.
For those reading this and are technically inclined, Iāve been working with Flutter for the past 2 years, and itās fantastic. So Iām thinking, if I am to work on another WaniKani app, itās gonna be built with Flutter, for Android and iOS (and potentially Mac/Windows/Linux). Itās also much much easier/simpler/faster to build apps with than native Android.
However, Iām not confident Iād have the stamina to build a production-ready app alone, on top of my full-time dev job and other projects. I would be totally up to set up a GitHub org and work with whoever is interested though. React or React Native experience translates very well to Flutter, for example, so if youāre in that camp, are willing to learn, and have the time, you could join up, and we could have a good time.
Iāve always done my own designs, but itās just been what I feel looks nice and is good design ā no real expertise. So if we do assemble a team, and if youāre a designer whoād be willing to help out, Iād gladly welcome input from you.
So yeah⦠If thereās anyone interested in any way, Iām definitely down to talk.
It wasnāt a mistake, official apps are in development, but it looks like they are still pretty far off. And even if/when the official apps arrive there will still be a place for unofficial ones like mine (and hopefully more - choice is good). Some of the most popular features in Flaming Durtles for example are inspired by userscripts and are the kind of features that the WK devs will almost certainly never put into an official app.
I realized you were the dev of Flaming Durtles shortly after posting my previous message. Hey there. I would offer something like joining forces to make Flaming Durtles look fancy or something, but you seem to be doing native Android so whateverā¦
I agree, and youāre right. Maybe Iāll start a project sometime and do some groundwork, then see if anyone wants to join the effort in a new thread.
Yeah, my Java day job made that an easy decision, as well as the fact that Iām moving away from using iOS and I really, really donāt want to deal with the criminally abusive App Store policies, which are affecting iOS WK apps as well. So I donāt need cross-platform support.
FD is definitely not a pretty beast, but itās always been my priority to keep the UI simple, fast and efficient. And when I look at what passes for good app UI design these days I see too much form over function, too much bling and bloat at the price of usability, too many people who think they know what āusabilityā means but really donāt. I know there must be a nice middle ground there, but until I find it I have firmly chosen one side of that raging river . I know itās not to the taste of some people, but thatās the price of letting a backend dev do frontend design without proper training
Haha. I can respect that. Iāve known a few others with similar opinions and I think you make a fair point, although I guess I prefer to get as close to the middle ground as I can.
As for iOS, I couldnāt agree with you more. Just the other day, an app we built for a client got rejected after initially being approved, and who knows what will happen now. Appleās developer practices, and especially the App Store, singlehandedly make me want to switch away from mobile development sometimes.
At the end of the day, though, so many potential users are on iOS that you canāt just ignore it as a business. And in the case of a potential WK app built with Flutter, the work to get it to iOS is so little besides the struggle with the App Store that the the number of users who might benefit from me biting a bit of that bullet kind of makes it worth it. I still rage when something negative happens, butā¦
Hereās hoping these antitrust investigations yield some results.