VoiceLink Beta Testers Wanted ... A New Accessible Way to Connect

instead of all the fancy imojes please ensure the links are clickable when using screenreaders as not a good start, in terms of accessibility to even get more info on the app.

the reason the testflight is not working on iOS is because it's for macOS, as evendenced by this thread.

I was able to access the test flight link but doing it manually but I’m not very impressed with just the layout over all, it is very confusing and almost overwhelming.

for a developer who claims to be building an accessible community type app, the testflight link and the link to the website is inaccessible. this is a huge oversite, and should be rectified. I will not test until you have an accessible testflight, link, as i cannot test with the current implimentation. good luck, but as someone said, not a great start.

Just by this post alone not a good look. Plus, not that hard to make clickable links. I'm not gunna wanna copy paste to a link that may or may not, work. What's wrong with people! Plus, clean up your sentences. Can't even read this shit! Links are all over the place on same lines, sentences are jumbled yeah. hard pass. Sighs what's wrong with some devs! If your app's interface is so confusing that your users cannot navigate and you claim to be a blind dev? wow! What did you just put this all into AI and called it a day because if ya did? I ain't going for that! my Gawd! Least put in some effort. Not lazy shit like this cause it damn well shows.

The link you provided in this post is not showing up properly as a clickable link. It’s appearing as plain text within your message.

Unfortunately the app keeps crashing after swiping to recent. I am using IOS 26.5 beta3.

Hi,

I'm looking forward to hearing the audio overview once it gets posted. I have seen other platforms like Zoom and team talk, but how is this app different compared to the platforms that we are already used to using?

I hope you ain't storing sensitive data in plain text. We do not need another TT clone.

Hi Dominique,

Thanks for sharing this. I'd like to give you some honest feedback, dev to dev (I'm developing TTAccessible with AI too, so I'm in the same boat).

On my end the app crashes pretty quickly, and I have to say the interface didn't feel very intuitive on first use. I'm not saying this to tear down your work, quite the opposite — but I get the feeling that some parts would benefit from more time spent on them, away from overly generic prompts.

One question out of curiosity: why combine Codex and Claude Code? Personally I only use one AI and I find it helps keep the code consistent. I'm a bit worried that using several tools in parallel could be counterproductive on a project like this.

AI is a great tool, but you really need to take the time to polish the interface behind it, especially for an app that's meant to be accessible. My app is far from perfect, but at a minimum it runs, and I've spent a huge amount of time on the VoiceOver UX.

Good luck, and feel free to reach out if you want to chat.

Mathieu

Yeah some gunna come at me but I do not care. To add to that, if you don't know a single lick of programming, don't even bother using AI if you don't even know how to fix your code and test your work properly. Man what is up with devs. I'm gunna keep on calling this shit out. If you prompt your shit into AI and call it a day with out testing, that's pure lazy and shouldn't even be taken seriously. I'm not saying you can't use AI to do the bulk of what you're doing but man, at least have some, experience and know how to fix, read and edit your code. You are not, a dev if you're just, only relying on AI and only going off of what it's coding with out taking a look yourself, because judging by the comments here I'm gunna go out and say this is exactly what you're doing. If you claim to be a blind dev, you shouldn't have any excuse for producing clunky interfaces like what I'm hearing here in this thread. Please prove me wrong but if you have an issue editing your dictated sentences, then I have no doubt you're having the same issues here as well. Do you know about while and for loops and if statements? Do you know about classes? variables? integers? floats? All, I think are basic programming concepts that I think every, single, dev, needs to know before diving into AI. I'm seeing devs not, on this forum but on others who code their shit into AI and don't even know how to fix their code that AI wrote. That's, bad!

I think Dominique is really trying to make something useful for us. I'm also working on a police scanner app for Windows, entirely using AI. I've tried to learn some basic C+ from Microsoft, but I stopped. I think it's great that you can even code using AI. What I did was every time I got an error, I asked ChatGPT what the error meant and how to fix it. Maybe that's what you should do. Some people told me that I didn't put much effort into my app, but I've spent hours working on it. I haven't worked on it lately, though.

AI is great but like anything it's a tool, if you just throw it a prompt and don't understand what it's doing when it comes to programming, then things are going to be broken a lot more than they are fixed.

I think the criticism is fair up to a point, but the real problem is not AI by itself. The real problem is people rushing unfinished work out the door and expecting the public to do the basic testing for them.

Using AI to help build something is one thing. Prompting an app into existence, doing little or no proper testing, and then immediately putting it in front of users is something else.

What people seem to be reacting to in threads like this is not "AI was involved", but "this feels half-baked, confusing, or broken, and it should have been tested more before being shown off". That is especially true for accessibility-focused software, where the basics really do need to be solid before you start asking blind users to try it.

So yes, AI can be useful. But it does not remove the need to think through the interface, test properly, fix obvious problems, and make sure the thing works on your own setup before you start inviting the public in.

Too often the vibe is less "here is a tested beta" and more "look what I just made, now everyone else can tell me why it broke". I think that is what people are actually frustrated with.

Okay, first, you know that's not how domains work! You can't just go and ask someone can I get it from you. Second, don't assume that someone here, on this forum, has it because pretty sure they don't. Third, Try another suffix or another combination if that one does not work. Not, the end of the world! If you really want that domain bad enough, if it's not for sale, deal. Second, if the person doesn't wanna make an offer which I'm sure that's your next step, again, deal! Either way you're gunna have to go through the registrar of which the domain is registered with first I believe to get that process started.

Hi Dom,

Can you please contact me at Michael@applevis.com? Emails going to you from the site's subscription functionality keep bouncing and returning to us as undeliverable. Thanks!

Good morning,
I'm using the latest beta version of the app under iOS 26.5 & can't sign-in using Mastodon.
If I try, I'm taken to a page which discusses how to download the app.
I also cannot contact the developer using any of the contact methods listed in the app.
Attempting to submit the form results in an error about a mismatched pattern.
Would anyone be willing to assist me?
The best way to reach me is via my personal contact for, here on AppleVis, though, I was able to leave feedback via TestFlight as well.
Any hints on why this is not working or what I may be missing are greatly appreciated.

I got an email saying that there was an update available, but TestFlight still insists on showing the older version.
I’m also having this issue with another app I’m testing. Is TestFlight down?

Hello,
I attempted to sign-in with Mastodon but after authorizing the app, the page I was redirected to showed a 404 error.

I went to the website provided at the top of the page and it just took me to a Web app version. I couldn’t find any link to a TestFlight beta for iOS

Ok, I know what you mean now. I tried it again and it’s still not working. It still shows that web app version

I’m looking forward to it.