TapType is out.
-
@fireborn Pretty cool! Found a couple of bugs for your enjoyment:
- in full screen landscape mode, the hide keyboard button doesn't work
- inserting punctuation deletes the character before the cursor, even if it wasn't the automatically inserted spacePixel 7 Android 16
@aburka when using fullscreen, try dismissing with a two finger swipe down
-
@fireborn Finally, a flicktype successor. I'll give it a try. I will probably make it my main when you add multiple languages available or Arabic to be more specific. Congrats on the release.
@quanchi thank you for giving it a try
-
@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.
@qgustavor @fireborn @larozeppeli
Please don't assume everybody shares the same concerns as you; here or elsewhere. There are plenty of Open Source people here, but also lots of people with no particular interest in it. OP has stated it's not open source at this point. Respect that and act accordingly. But please don't badger people about it. -
@qgustavor @fireborn @larozeppeli
Please don't assume everybody shares the same concerns as you; here or elsewhere. There are plenty of Open Source people here, but also lots of people with no particular interest in it. OP has stated it's not open source at this point. Respect that and act accordingly. But please don't badger people about it.@jannem @qgustavor @larozeppeli It likely will be, once I clean it up and make the code nicer to read for sighted users. Another thing I didn't mention because I didn't want to make it sound like contributions aren't welcome, they are. While I don't mind feedback and feature requests, I'm one person with limitted time. I don't have the spoons to sit through triaging Merge requests, and so they would just sit there and that's no fun for anyone.
-
@fireborn Pretty cool! Found a couple of bugs for your enjoyment:
- in full screen landscape mode, the hide keyboard button doesn't work
- inserting punctuation deletes the character before the cursor, even if it wasn't the automatically inserted spacePixel 7 Android 16
@aburka Fixed in next version
Thank you for trying TapType -
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 Is there any chance this would work on Jieshuo? My friend is looking for such a keyboard for so a long time, but she's using Jieshuo.
-
@fireborn Is there any chance this would work on Jieshuo? My friend is looking for such a keyboard for so a long time, but she's using Jieshuo.
@destranis It will, if they suspend browse by touch Or use a quick typing extention. Support would have to be added by The CSR developer
-
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 is it possible to port this to QWERTZ? That is the German keyboard. I am willing to help you test. Have 2 pixel pros and a few other androids.
-
@fireborn is it possible to port this to QWERTZ? That is the German keyboard. I am willing to help you test. Have 2 pixel pros and a few other androids.
@randomfelix I imagine that a port to qwertz should b easy enough, will look into it.
-
@fireborn Yeah, although I do think there's other stuff you could do paid features on, a screen reader just seems kinda... Idk how to describe it, I've seen it all over, Jisuo, Jaws and Supernova on Windows, it just feels off.
@alexchapman @fireborn
Are you volunteering to give the developer a living wage so he can donate the product of his labor while existing in our current society? Or do you really have the gall to demand he go into debt so you can have your app for free? -
@jannem @qgustavor @larozeppeli It likely will be, once I clean it up and make the code nicer to read for sighted users. Another thing I didn't mention because I didn't want to make it sound like contributions aren't welcome, they are. While I don't mind feedback and feature requests, I'm one person with limitted time. I don't have the spoons to sit through triaging Merge requests, and so they would just sit there and that's no fun for anyone.
@fireborn @jannem @larozeppeli
I wish I had lots of PRs in my projects. For me, often people just ask you to fix things but no one tries helping the issue. Sometimes they don't use the search and ask repeated things too.But FOSS is a great thing. Last November a guy sent a PR and GitHub never notified me of it, then they sent me a message and I noticed it. It was a loveful PR, fixed an issue I had not noticed. I hope people will help you and you will have a great experience with it.
-
@alexchapman @fireborn
Are you volunteering to give the developer a living wage so he can donate the product of his labor while existing in our current society? Or do you really have the gall to demand he go into debt so you can have your app for free? -
@fireborn @jannem @larozeppeli
I wish I had lots of PRs in my projects. For me, often people just ask you to fix things but no one tries helping the issue. Sometimes they don't use the search and ask repeated things too.But FOSS is a great thing. Last November a guy sent a PR and GitHub never notified me of it, then they sent me a message and I noticed it. It was a loveful PR, fixed an issue I had not noticed. I hope people will help you and you will have a great experience with it.
@qgustavor @jannem @larozeppeli I would love this if I actually had the time to review them. I don't.
-
@qgustavor @jannem @larozeppeli I would love this if I actually had the time to review them. I don't.
@fireborn@dragonscave.space @qgustavor@urusai.social @jannem@fosstodon.org definitely malware
-
@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
