Re: braille me display not quite ready
erik burggraaf <erik@...>
toggle quoted messageShow quoted text
Hello, I enjoyed reading your comments, and I agree with a lot of what you had to say. However, I disagree with your assertion that Braille me is quote not ready quote. based on your comments, the only potential showstopper that I see is the fact that some of the dots do not go all the way down below the faceplate. I would be interested to know how many Braille me units you tested, and whether this issue appears on any other units. if anybody else has tested a braille me, I hope you will chime in and let me know. if you were saying that batteries and charging devices were catching fire, ports were collapsing, or the device was particularly susceptible to damage by dropping, then I would say maybe we need to go back to the drawing board here. However, most of the issues are software and firmware related. Many of these things can be tweaked in the context of the current device.
It's a great rundown of potential bugs, and feature suggestions. However, I seriously doubt that all users need access to all of the features you specified. Not all users need access to 25 different languages for example. many languages will not be considered for addition, until the countries that predominantly use those languages consider adopting Braille me. language switching on the Fly is also something that can and should get better over time.
support for entering text and using modifier Keys is important to me, but may or may not be important to somebody else.
It seems to me that you got really excited about a great new device, and created some unnecessarily and perhaps unreasonably high expectations for what it could do, especially in a first release. I don't know how well the Braille me stacks up to the orbit in all of the areas you specified for example. However, the orbit is 2 years behind production, and almost no one can get their hands on it. to me, that indicates that something about the orbit or its processes is quoteaccess technology world. We know they will put out great Hardware with Hokie software, and then make software improvements catch-as-catch-can. But we know those improvements will come.by comparison, I recently did a customer training on a braille sense Polaris for work. the only fully functioning app in the Braille sense Polaris right now as far as I'm concerned is the word processor. However, even the word processor is limited for example, it is not currently possible to print from the word processor without installing a third party app. the rest of the office apps that come with Polaris sweet are read-only apps, which basically convert spreadsheets and slideshows into HTML format with no formatting, and allow a user to read the information. the Wi-Fi utility that comes with the sweet does not support connecting to WPA2 Enterprise networks, and such corporate networks need to be connected through Android stock Wi-Fi utility, which in the Polaris, has some minor accessibility issues. Browsing websites with the on-suite browser app is extremely barebones. it does not currently support navigating by headings, tables, lists, and other HTML attributes. the Polaris supports installing third-party synthesizers, however, third-party synthesizers can only be activated and used in the stock Android outside of the proprietary application sweet. so, as much as I like the hardware in the Braille sense Polaris, when I think of the functionality I get from my HTC phone connected to a braille Edge, versus what I get from the firmware in the Polaris, I cannot help being extremely disappointed, especially considering the difference in price. Does that mean the Braille sense Polaris is not ready? Well, in my mind, yes I think it does. However, the customer I trained absolutely loved it. despite the high price and the extreme limitations, it does everything she wanted it to do, and it does so very well. Should GW micro have waited until they had a fully functioning set of onsweet apps before releasing the Polaris? Yes, in my opinion they should. However, we have a happy customer now, and the product is generating income for the company, which can hopefully be used to justify further feature improvements down the road.
Hims is a known quantity. We know they consistantly put out great hardware with hokie software and make substantial improvements over time. Innovision is an unknown. We don't know what to expect, although they have been very responsive to me personally despite the fact that I haven't been able to go forward. I completely understand your disappointment, but I suggest patience as this is a first release of a new product and is not going to have everything all at once. I believe innovision is able to fulfill orders at this point, which is more than the cometition can say. Others on list are reporting that early hardware issues are being addressed, and generally I have not heard evidence that the company acted in bad faith other than one third hand complaint from some one high up in a blindness organisation with a vested interest in a direct competeter product.
So all in all, I think based on what you wrote, the assertion of not ready gives an entirely false impression while your document conveys worth while information.
On June 23, 2018 9:20:17 AM "Josh Kennedy" <joshknnd1982@...> wrote:
here are all the reasons why braille me is not ready. note, this is also a google doc that i shared with innovision themselves.