TapType is out.
-
@4censord You could add them to the user dictionary and they would get prioritized, but I'll look into adding other languages.
@fireborn It feels quite nice to use. definetly looking forward to more languages. For now i will just fight The suggestions
-
@fireborn It feels quite nice to use. definetly looking forward to more languages. For now i will just fight The suggestions
@fireborn Though it's quite a lot harder than with what i'm using rn.
-
@fireborn Though it's quite a lot harder than with what i'm using rn.
@fireborn funny bug i've encountered: i'm unable to add the comma to the punctuation menu. anything else works just fine. but comma refuses for some reason.
-
@fireborn funny bug i've encountered: i'm unable to add the comma to the punctuation menu. anything else works just fine. but comma refuses for some reason.
@4censord I fixed it in 1.0.2

-
@4censord I fixed it in 1.0.2

@fireborn nice, works perfectly!
-
@fireborn nice, works perfectly!
@4censord I found it while trying to do this exact thing haha.
-
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@marcozehe guck mal, das erinnert mich doch an ein kleines UI-Projekt, das wir mal zusammen machen durften

-
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@dragonscave.space where's the repo with the source?
-
@fireborn@dragonscave.space where's the repo with the source?
@larozeppeli Source code isn't publicly avilable yet.
-
@larozeppeli Source code isn't publicly avilable yet.
@fireborn@dragonscave.space because...?
-
@fireborn@dragonscave.space because...?
@larozeppeli I'm sorry, I wasn't aware on fedi you had to justify software distribution decisions. Because the code is a bit of a mess, as it was originally tied into another project that I then brought it out of because that project is months away and this solves a problem right now.
-
@larozeppeli I'm sorry, I wasn't aware on fedi you had to justify software distribution decisions. Because the code is a bit of a mess, as it was originally tied into another project that I then brought it out of because that project is months away and this solves a problem right now.
@fireborn@dragonscave.space I don't see how the code being messy makes it bad for you to release it, I just have the hunch its malware but I really like the idea so it would be nice to see the source
-
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 OMG dude if I had flicktype back on iOS I might have a reason to get a bigger phone.
-
@fireborn@dragonscave.space I don't see how the code being messy makes it bad for you to release it, I just have the hunch its malware but I really like the idea so it would be nice to see the source
@larozeppeli It isn't malware, but if you don't want to you don't have to turn on the accessibility service. It doesn't request any other permissions, other than record audio if you don't have a voice input IM configured and try to use that feature. You can reject everything and block network access and everything will still work. It doesn't even make network connections. I thought about including an updater like my MUD client has, but decided against it because fundamentally I'm against an input method having any network connectivity.
-
@larozeppeli It isn't malware, but if you don't want to you don't have to turn on the accessibility service. It doesn't request any other permissions, other than record audio if you don't have a voice input IM configured and try to use that feature. You can reject everything and block network access and everything will still work. It doesn't even make network connections. I thought about including an updater like my MUD client has, but decided against it because fundamentally I'm against an input method having any network connectivity.
@fireborn@dragonscave.space I'm not installing it until I see (pun intended) the source, what's the big deal?
-
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 I'm sighted and honestly this sounds better than most existing keyboards.
-
@fireborn I'm sighted and honestly this sounds better than most existing keyboards.
@retrosponge Feel free to try it. I haven't tested it for sighted users, but if you can come up with actionable ways I could make it better I'm all ears. You'll still have the tts output because that is sort of the point, but feel free to turn it off if you find it unhelpful.
-
@retrosponge Feel free to try it. I haven't tested it for sighted users, but if you can come up with actionable ways I could make it better I'm all ears. You'll still have the tts output because that is sort of the point, but feel free to turn it off if you find it unhelpful.
@fireborn I will give it a look.
-
@larozeppeli It isn't malware, but if you don't want to you don't have to turn on the accessibility service. It doesn't request any other permissions, other than record audio if you don't have a voice input IM configured and try to use that feature. You can reject everything and block network access and everything will still work. It doesn't even make network connections. I thought about including an updater like my MUD client has, but decided against it because fundamentally I'm against an input method having any network connectivity.
@fireborn @larozeppeli Let me tell you one thing:
You are on the Fediverse, people here is using a social network with less people than closed source alternatives because (at least for many people) they like the idea of open source, so they expect apps to be open source.
If your code is bad, people can help you. As long you didn't put a password or API key on there, you can just publish it.
If you hide the source code, people might not trust you, people might think your code might be malware (even if you say it isn't) or have a hidden bad thing.
You will have more luck having people to download your closed-source app by sharing it on closed-source social networks, people there don't bother about it. People here bother about it. People here bother about their security and privacy.
-
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 @alexhall Haven’t tested this yet, but this sounds great! Especially because we might be able to run it in work profiles (the TalkBack Braille IME can’t run there). In place of pure beam search against a dictionary, have you considered something like GPT-2 or another very small (by modern standards) language model? You’d probably get near-realtime inference on most mobile chips. Also the source code doesn’t seem to be in that repo