TapType is out.
-
@fireborn@dragonscave.space @qgustavor@urusai.social @jannem@fosstodon.org definitely malware
@larozeppeli @jannem @qgustavor I'd like to see some actual proof, rather than what you're currently doing. Which is a lot of nothing.
-
@4censord I found it while trying to do this exact thing haha.
@fireborn so I've just tested 1.2, and that made predictions much worse for me. While its more forgiving, it now usually takes me 1 or 2 "next prediction" swipes to get to the wanted word.
(I have not yet tested 2.0, but will do so next)
-
@fireborn so I've just tested 1.2, and that made predictions much worse for me. While its more forgiving, it now usually takes me 1 or 2 "next prediction" swipes to get to the wanted word.
(I have not yet tested 2.0, but will do so next)
@4censord I rewrote the algorithm for version two
-
@fireborn so I've just tested 1.2, and that made predictions much worse for me. While its more forgiving, it now usually takes me 1 or 2 "next prediction" swipes to get to the wanted word.
(I have not yet tested 2.0, but will do so next)
@fireborn oh I see 2.0 has more languages, thank you so much!
Would it be possible to have an option to just add German to the prediction corpus, as opposed to having a separate keyboard (and layout)?
Also I see there is sponsors now, i'll throw some money your way later
-
@4censord I rewrote the algorithm for version two
@fireborn oki, testing that right now and it does feel better.
thanks! -
@fireborn oh I see 2.0 has more languages, thank you so much!
Would it be possible to have an option to just add German to the prediction corpus, as opposed to having a separate keyboard (and layout)?
Also I see there is sponsors now, i'll throw some money your way later
@4censord i tried it, and it made predictions super unreliable. I'm open to trying again, but I thought it more important to get individual support working so it was at least an option
-
@fireborn oki, testing that right now and it does feel better.
thanks!@4censord You're welcome
-
@4censord i tried it, and it made predictions super unreliable. I'm open to trying again, but I thought it more important to get individual support working so it was at least an option
@fireborn I see yeah. with my traditional keyboard it took quite a while to train it for both languages to not be annoying, so I can see that yeah.
-
@fireborn I see yeah. with my traditional keyboard it took quite a while to train it for both languages to not be annoying, so I can see that yeah.
@4censord I'm also not a german or spanish speaker, so I wouldn't know how to weight the words in the prediction algorithmwhen weighing likelihood against english words, though I suspect that's very personal.
-
@fireborn OMG dude if I had flicktype back on iOS I might have a reason to get a bigger phone.
-
TapType is out. It's a keyboard for blind Android users.
There are no visible keys. You tap where QWERTY keys would be from muscle memory, and a spatial prediction algorithm figures out what you meant. It scores nearby keys using a Gaussian proximity model and runs a beam search against an 80,000 word dictionary. You don't need to be precise. That's the whole point.
Swipe right to commit a word. Swipe down or up to cycle through suggestions. Swipe left to delete. It learns what words you use most and ranks them higher over time, and you can add your own words to a personal dictionary.
Every letter has its own unique sound, from Andre Louis's keyboard sound recordings, so you can learn to identify keys by ear without relying on speech. Each swipe direction has a distinct sound too. TTS is there when you want it, adjustable speed, and you can turn it off entirely if you prefer sounds only.
It has emoji search with skin tone selection and favourites, a number pad mode, an upper case mode, and full punctuation support with a customizable quick list. Two-finger gestures handle things like send, close keyboard, switch keyboard, and voice input.
Everything works with TalkBack. I built this because FlickType was a fantastic keyboard for blind iOS users and then it was gone. Nothing like it existed on Android, so I made one.
It's free, no ads, no tracking, no metrics. I'm not evil.Edit: Now on 2.0 with multiple languages supported.
If you find TapType useful, consider supporting its development:
https://paypal.me/aaronhewitt
https://github.com/sponsors/aaron-gh
https://liberapay.com/fireborn/Download: https://github.com/aaron-gh/taptype-releases/releases/latest
#TapType #Accessibility #A11y #Android #Blind #VisuallyImpaired #TalkBack #Keyboard #AssistiveTech@fireborn Sounds really cool. I'd imagine that sighted users can also gain a speed boost, so I'll have to try it
-
@fireborn Sounds really cool. I'd imagine that sighted users can also gain a speed boost, so I'll have to try it
@Curve25519 Possibly, that depends what you're moving from. I'd be interested to know if you do.
-
@Curve25519 Possibly, that depends what you're moving from. I'd be interested to know if you do.
@fireborn I can't find the source code, mind sharing?
-
@fireborn I can't find the source code, mind sharing?
@Curve25519 Not yet available, unfortunately. Mostly because the idea of other people submitting merge requests I don't have the time to review or triage is daunting over anything else.
-
TapType is out. It's a keyboard for blind Android users.
There are no visible keys. You tap where QWERTY keys would be from muscle memory, and a spatial prediction algorithm figures out what you meant. It scores nearby keys using a Gaussian proximity model and runs a beam search against an 80,000 word dictionary. You don't need to be precise. That's the whole point.
Swipe right to commit a word. Swipe down or up to cycle through suggestions. Swipe left to delete. It learns what words you use most and ranks them higher over time, and you can add your own words to a personal dictionary.
Every letter has its own unique sound, from Andre Louis's keyboard sound recordings, so you can learn to identify keys by ear without relying on speech. Each swipe direction has a distinct sound too. TTS is there when you want it, adjustable speed, and you can turn it off entirely if you prefer sounds only.
It has emoji search with skin tone selection and favourites, a number pad mode, an upper case mode, and full punctuation support with a customizable quick list. Two-finger gestures handle things like send, close keyboard, switch keyboard, and voice input.
Everything works with TalkBack. I built this because FlickType was a fantastic keyboard for blind iOS users and then it was gone. Nothing like it existed on Android, so I made one.
It's free, no ads, no tracking, no metrics. I'm not evil.Edit: Now on 2.0 with multiple languages supported.
If you find TapType useful, consider supporting its development:
https://paypal.me/aaronhewitt
https://github.com/sponsors/aaron-gh
https://liberapay.com/fireborn/Download: https://github.com/aaron-gh/taptype-releases/releases/latest
#TapType #Accessibility #A11y #Android #Blind #VisuallyImpaired #TalkBack #Keyboard #AssistiveTech@fireborn woah. Real curious about what are these special keyboard key sounds. Hmm I guess the easiest way for me to check them out is to grab my old Android and try the app out -
T tanyakaroli@expressional.social shared this topic
