# Suggestion for typos

**URL:** https://community.wanikani.com/t/suggestion-for-typos/63587
**Category:** WaniKani
**Created:** [October 20, 2023, 3:56pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587 "2023-10-20T15:56:03Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Zichqec](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/zichqec/32/707630_2.png) [@Zichqec](https://community.wanikani.com/u/Zichqec)
#### Post date: [October 20, 2023, 3:56pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/1 "2023-10-20T15:56:03Z")

</div>

Is this the right place to make suggestions? I hope so.

Anyways, I primarily use WK on my phone, and some of my most frequent mistakes are from typoing readings because my phone’s keys are just so darn small. Every time it happens, it’s frustrating, because I _do_ know the answer and I said the right thing in my head, but I didn’t notice that I accidentally pressed ki instead of ko, or gio instead of gyo, etc. because I was moving quickly.

And I keep thinking to myself, it would be really nice if WK would notice that I _don’t open the tab to check the reading_ in those cases, and if I answer the reading correctly when it comes up again, it doesn’t knock me down a level in the SRS. If I know the reading on my own without having to check, then I probably knew it in the first place and just typoed, so cut me a break yeah?

Theoretically this could also be combined with a check to see if the mistake was a one letter typo, if you really want to tighten it up to only catch typos and not someone thinking totally the wrong reading.

I really wish this were a thing because it sucks to be forced to do extra reviews just because I pressed any one of Y, U, I, or O when I didn’t mean to, and they’re all so close together… I’d even accept just staying at the same level of the SRS because I made a typo, just don’t knock me back down a level when the mistake wasn’t related to knowing the kanji.

Hopefully as I get further in I’ll get faster at reading kana and notice typos before I press enter 😅

---

<div class="post-metadata">

### Author: ![doublemc](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/doublemc/32/621990_2.png) [@doublemc](https://community.wanikani.com/u/doublemc)
#### Post date: [October 20, 2023, 4:00pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/2 "2023-10-20T16:00:03Z")

</div>

this is the right place for a suggestion!

yeah, like, why do we get knocked _down_ a level when we get it wrong? why not just keep it the same?

---

<div class="post-metadata">

### Author: ![Zichqec](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/zichqec/32/707630_2.png) [@Zichqec](https://community.wanikani.com/u/Zichqec)
#### Post date: [October 20, 2023, 6:35pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/3 "2023-10-20T18:35:12Z")

</div>

I don’t mind getting knocked down a level if I actually get it wrong, because if I’m getting it wrong I want more chances to practice to make sure I’ve really got it. I just think that typos should be treated differently from actually getting it wrong 😅

---

<div class="post-metadata">

### Author: ![HA472](https://cdck-file-uploads-global.s3.dualstack.us-west-2.amazonaws.com/wanikanicommunity/original/3X/f/d/fd4c154120954695f788402f3bcf4e616499bc2d.png) [@HA472](https://community.wanikani.com/u/HA472)
#### Post date: [October 20, 2023, 8:04pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/4 "2023-10-20T20:04:51Z")

</div>

Since you do Wanikani on a phone, you should consider using a 3rd party app instead of the browser/web app. The 3rd party apps below have built in undo buttons.

Android:

1. [Smouldering Durtles](https://community.wanikani.com/t/android-smouldering-durtles-v107-native-app-with-offline-lessons-and-reviews-plus-themes-and-script-like-features/61776)
2. [Hakubun](https://community.wanikani.com/t/hakubun-cross-platform-app-for-wanikani-android-alpha-version-released/62646): Alpha version released
3. [Flaming Durtles](https://community.wanikani.com/t/android-flaming-durtles-android-app-with-offline-support/38400): Unsupported (may or may not work properly with kana vocabulary)

Apple:

1. [Tsurukame](https://community.wanikani.com/t/ios-tsurukame-native-app-with-offline-lessons-and-reviews/30635)
2. [Hakubun](https://community.wanikani.com/t/hakubun-cross-platform-app-for-wanikani-android-alpha-version-released/62646): iOS app will eventually be released
3. [Jakeipuu](https://community.wanikani.com/t/iosandroidwindows-jakeipuu/45634): Unsupported (However, if you have done all your kana vocabulary reviews & lessons, it has a cool reading practice feature. The app doesn’t work with kana vocab.)

---

<div class="post-metadata">

### Author: ![WeebPotato](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/weebpotato/32/679291_2.png) [@WeebPotato](https://community.wanikani.com/u/WeebPotato)
#### Post date: [October 20, 2023, 9:05pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/5 "2023-10-20T21:05:53Z")

</div>

> [@doublemc](#):
>
> yeah, like, why do we get knocked _down_ a level when we get it wrong? why not just keep it the same?

That’s a part of how a SRS works. If you get something wrong, it means you may need to be reminded of it more often. Anki works the same way. Keeping items on the same level would potentially make the SRS less effective.

---

<div class="post-metadata">

### Author: ![ctmf](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/ctmf/32/183394_2.png) [@ctmf](https://community.wanikani.com/u/ctmf)
#### Post date: [October 21, 2023, 1:27am UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/6 "2023-10-21T01:27:29Z")

</div>

So this isn’t literally an answer to the question, but maybe a helpful tip:  
Using the iPhone’s (maybe the same on android, can’t say) kana flick keyboard instead of a QWERTY one… takes a little learning, but once you do the typos on readings go way down.

And before you get good at it, it forces you to slow down and pay attention to what you’re typing. win/win

Bonus, you’re simultaneously learning to type in Japanese on your phone. win/win/win

---

<div class="post-metadata">

### Author: ![Gorbit99](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/gorbit99/32/7307_2.png) [@Gorbit99](https://community.wanikani.com/u/Gorbit99)
#### Post date: [October 21, 2023, 3:54am UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/7 "2023-10-21T03:54:05Z")

</div>

This. I too have fat fingers, and I really struggled with typos until I switched to flick. Now I don’t really make typos like that.

---

<div class="post-metadata">

### Author: ![Zichqec](https://sea1.discourse-cdn.com/wanikanicommunity/user_avatar/community.wanikani.com/zichqec/32/707630_2.png) [@Zichqec](https://community.wanikani.com/u/Zichqec)
#### Post date: [November 17, 2023, 4:17pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/8 "2023-11-17T16:17:54Z")

</div>

I appreciate this suggestion and I do want to do it, but unfortunately right now that adds an extra layer of complexity that makes my brain want to put off doing my reviews, which ultimately is worse for me than a few typos. I think I’ll try to do it once some irl stuff clears up for me though.

I think I misremembered the WK info as saying not to use jp input, but it actually is worded to say that you don’t _have_ to, not that you _can’t_. So, thanks for helping me correct that thinking!

(Sorry for the late reply lol, aforementioned irl stuff)

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/wanikanicommunity/original/4X/6/2/a/62a8b0f4c59ff2c5b6651ffcf43531480b3e5297.png) [@system](https://community.wanikani.com/u/system)
#### Post date: [November 16, 2024, 4:18pm UTC](https://community.wanikani.com/t/suggestion-for-typos/63587/9 "2024-11-16T16:18:56Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
