Re: Is Buster still in development?
Justin Mann
The truth is because I do work with accessibility-related stuff, I do have to be careful, we have a decent group of hams that work for Apple, and one of the things I’d love is to have a
toggle quoted messageShow quoted text
mac-native solution to program some radios, because the mac OS platform does have some native accessibility built right in to the operating system that a dev can take advantage of. I know how to go through an app, and I know what code needs to be modified to make an app work with voiceover for instance. Were I to pull the project from github, and then try and modify, and republish the source code, it would go against my NDA… it’s one of the hoops that you pay for for having a job working for a decent company. I’d love to have the ability to use Android as a blind person, and know that I could pickup any android device and know that the app is accessible, and I hope someday that the operating system gets it. However, due to Android’s fragmentation, app developers can’t just decide they’re going to write code in this manner, and voila they have an accessible app. Because iOS is what it is, you cna publish code using native controls, native calls to APIs, and accessibility, just happens. That being said I don’t want to get too much in the politics of iOS verses Android in this discussion, but i do appreciate your insight.
|
|