Following up to this post https://lemmy.ml/post/31598540
A number of people asked for F-Droid support when I posted about my Lemmy client, and it’s here!
I didn’t notice the scope of some of the app permissions until now, but half of those are unnecessary. I’ll be reducing the scope in the next release to avoid any confusion.
I am a TalkBack screen reader user and I’m downloading your app to test it with accessibility services right now.
I haven’t done any testing with a screen reader, but I would love to work with you to make the app more accessible.
I would love to help. It’s actually not as bad as it could be from what I can tell. Like sure, there are some issues, but trust me, I’ve seen way worse.
Blorp is actually a web app in a native app wrapper. I have some experience building accessible websites, but I wasn’t sure that it would translate well in the native app wrapper. But I’m really happy already somewhat accessible!
Wow, I certainly couldn’t tell that. It feels totally native. Not like a web app at all.
Thank you, well done!
I been keeping it updated via obtainium. It’s faster to get updates that way.
Yeah. F-Droid has some considerable lag in deploying new versions. I’m new to F-Droid but a 3-6 day delay in publishing new versions seems typical.
F-Droid’s big “thing” is reproducible builds. You could theoretically post any artifact to GitHub, so I have to trust that every update the artifact you built matches the source code. F-Droid allows me to know that the artifact matches the source code.
Unless of course you’ve implemented your own reproducible build system.
The caveat here is it means F-Droid has to build your app, which can take some time (but they’re actively working on improving that)
Yeah. Sorry I should have phrased my comment better. I’m not saying that’s a bad thing, but people should understand that the tradeoff of reproducible builds is a slight lag in updates.
No worries, I just wanted to explain why it takes time in case somebody didn’t know
Thanks! Apologies for the accessibility issues, but I’ll start working through your list!
Hey, not a problem. Most people don’t necessarily have to think about the accessibility for screen reader users. That’s what I’m here for.
