TapType is out.

[fireborn@dragonscave.space]

@jonathan859 Yeah, I was going to suggest turning on google voice typing and try that.

[alexchapman@vee.seedy.cc]

@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.

[fireborn@dragonscave.space]

@alexchapman The core functionality will be free. The only things that will be paid are anything that cost me money to maintain.

[freya@social.highenergymagic.net]

@fireborn @jonathan859 yep, talkback passthrough doesn't work here either. no other accessibility services on, pixel 8 pro, latest android, latest talkback.

[alexchapman@vee.seedy.cc]

@fireborn Right, so things like anything that requires some sort of server to function, that sort of thing. I've thought about doing stuff like that, but I've always said to myself if there's ever gonna be monitisation in any software that I do, I'm gonna do it where its completely optional, where the software is open source, and the only thing that's a paid thing is certain features running on my infrastructure. If people don't wanna pay, they can selfhost the full stack. That's the only way I'd ever do stuff like that.

[fireborn@dragonscave.space]

@freya @jonathan859 Interesting. Tap once and then keep tapping? you have to tap once to focus it.

[freya@social.highenergymagic.net]

@fireborn @jonathan859 yeah, that just makes the talkback "nothing here" boop

[jonathan859@someplace.social]

@fireborn Also added it to the list at androida11y.com/apps.

[fireborn@dragonscave.space]

@freya @jonathan859 interesting, looking into it. I don't have a pixel, so I got it to work on a samsung and figured that would be fine. haha.

[jonathan859@someplace.social]

@freya @fireborn Lol, typical TalkBack. Maybe it has to do with the Pixel part? I think Aaron is on Samsung while we're on Pixels.

[freya@social.highenergymagic.net]

@fireborn @jonathan859 I just got an 8 pro and um. wow android has come a long way., talkback is still not as fast as voiceover but.... I presume there's reasons for that?

[fireborn@dragonscave.space]

@freya @jonathan859 Reasons for that can quite simply be boiled down to talkback sucks.

[davidgoldfield@allovertheplace.ca]

@clv1 @fireborn Yep, I think Flicktype was the successor to that program. I wish someone would develop something like it today.

[freya@social.highenergymagic.net]

@fireborn @jonathan859 and ToBeSaid is a glitchy mess, wow, hoily shit

[freya@social.highenergymagic.net]

@fireborn @jonathan859 will it generate a custom voice? yes. will that work with talkback? no. will it slow my entire phone down to where it takesd a solid 2.5 seconds to recognise a talkback gesture? also yes

[jonathan859@someplace.social]

@freya @fireborn Lol yup, tried it. Heck na.

[fireborn@dragonscave.space]

@freya @jonathan859 Yup, it's very slow right now. Apparently it's being worked on though. Interestingly I have less issues than most with it.

[freya@social.highenergymagic.net]

@fireborn @jonathan859 also do you know if there's a workable eloquence or vocaliser that won't shit the bed due to licensing and/or direct boot? and/or is there a prebuilt copy of the GrapheneOS TTS? I'm using google right now

[fireborn@dragonscave.space]

@freya @jonathan859 eloquence is on the play store, that's the only way to get that. SmartVoice has a method of installing vocalizer voices, but I've not looked into how to do it.

[jonathan859@someplace.social]

@freya @fireborn RH Voice and E-Speak are the fastest you get atm. We need more and better TTS for Android. And a proper SR, but hey Aaron is working on that. I still have some faith in Android.