currently I’m using SwiftKey on my phone. I changed the input method to flick bc I thought most Japanese people use it as well and tbh it’s kinda hard to get used to.
what’s are your preferences?
1 Like
I’m using the romaji input becuase it feels easier to me. But, I’ve heard some people argue here that flick is better in the long run. I’ll keep an eye on this thread to see what everyone else says.
1 Like
I personally use a flick keyboard, but I don’t know if I can give any good arguments for using it or not using it. You will get used to it eventually if you keep using it though.
7 Likes
I want to add to this that once you do get used to the flick keyboard, you will be faster than with a romaji keyboard, so that’s how it pays off in the long run 
I like using it because it makes the kanji suggestion more accurate as well! (in my experience)
7 Likes
I use the flick one, having gotten used to it somewhat I find it more comfortable. With the romaji keyboard I can’t use the swipe functionality like I do for other languages, and without that I keep fat-fingering things and typing ‘s’ instead of ‘a’ or the other way around.
This is actually a major source of annoyance when doing WK reviews on mobile, but switching between regular for meaning and flick for reading would be even more annoying, so I use romaji there.
5 Likes
What the flippity-heck is a flick keyboard and how do I try it out?
7 Likes
This kind.
On Android i use
https://play.google.com/store/apps/details?id=com.google.android.inputmethod.japanese
6 Likes
I use flick, personally. I understand why someone would use romaji, though (especially since that’s what I use on PC).
4 Likes
Ooo I see, I had no idea this existed somehow, thank you!
1 Like
I use SwiftKey too, with ローマ字 input, and honestly it’s the fastest way to input Japanese. The predictive autocorrect that learns from you as you use the keyboard is awesome, and the muscle memory I’ve spent the last 30 years developing for qwerty keyboards gets put to really good use. I tried learning flick for a long time but I could just never get fast enough with it. When SwiftKey introduced Japanese for the first time it was romaji only so I got used to that super fast and when they introduced flick input too I just felt like I didn’t need that, really.
3 Likes
i use flick, it’s just easier for me to deal with the buttons… they’re bigger than the keyboard for romaji input.
4 Likes
I don’t type Romaji. I have used SwiftKey or the Google Japanese input. I switch between English and Japanese for reviews for definitions and pronunciations. I directly type in the Kana and Kanji.
didn’t know you could also use swipe on flick. how does it work? also I checked SwiftKey and apparently it doesn’t have swipe for flick input
I mean that I use swipe for English, German, Dutch, w/e on my QWERTY keyboard. And that, as far as I could tell I couldn’t use it on QWERTY for Japanese.
2 Likes
I use the flick keyboard. It’s odd at first and might take you a year or two to get really fast with it but it’s not so bad.
Isn’t this already in discussion?
2 Likes
this is me for sure!
1 Like
ahh I see. guess I misread your comment. Is german your native language or did you learn it? I’m living in germany btw that’s why I’m asking 
I’m German, living in the Netherlands, that is why Dutch is on that list.
1 Like
I thought there was no point to learn a new keyboard, and then I’ve just understood how works the flck keyboard. Wow, that thing looks so efficient and intuitive. I’ve not tried it yet, but now I just don’t get how it could be less efficient than a small qwerty phone keyboard, even for a beginner. Querty on phone sucks so badly. Edit: just look at my typos.