Need help with sourcing components for a prototype
docs.google.com
docs.google.com
An alternative could be talking with blind people in the third world, maybe this single cell solution would be good enough for them ?
The other option is to really work on basic mechanisms to make the basic cell far cheaper. For example [1] , which uses electrodes and small electric current as the basic sensations(not sure if good idea).
Also , there's a company called senseg doing tactile displays for tablets. Since tablets have quite a large area(and the price of components is highly constrained), and a braille strip could need far less,maybe they could offer a cost competitive solution. And they also have an sdk(and maybe tablets).
[1]http://aac-rerc.psu.edu/wordpressmu/RESNA-SDC/2013/06/19/pan...
I've been thinking about how to approach the blind community with the idea. My feeling right now is I should at least have something to "try out" to give them a sense of what I'm after. As soon as I figure out how to get the "reader" down to a size where I feel good about its usability (doesn't matter too much if wires are sticking out etc.) I just want the actual interface to be an appropriate size.
Another thing that is also "pie in the sky" but I think another reason I'm so interested is I think there are alot of applications (some reasonable today, but some that may be pushing the boundaries of what we may think of today).
I can imagine (at low enough cost, and by perfecting the mechanics) an entire industry could be born around the idea of "consuming information tactilely". Even for sighted people.
As for small components - maybe wait for the apple watch teardowns ,they'll tell which components have they used for the taptic engine.
This and the other links might be decent starting materials.
http://www.utopiamechanicus.com/article/open-source-hardware...
http://www.instructables.com/id/Brail-language-cell-phone-fo...
I wouldn't be surprised if 3d printers could enable cheaper readers(both by the ability to try many ideas, and using them as a low-volume manufacturing tool to start). But i think you also need to check patents in this field.
It appears those implementations are far larger than I anticipate my prototype would be. In fact the hobbyist solenoids I found were already pretty small (around 1" x 1/2"), but I'm looking for something even smaller (ideally the end prototype would be something a person could attach to their wrist or just hold in one hand.
And with today's components being so small I'm thinking (distant future) you could have a camera that would take a photo, then send the photo of text wirelessly to a server where it would perform OCR then send back instructions. Perhaps it has GPS.
I did think about navigation, which could be hard to get right. I get the impression there are probably only a few essential operations for something like that. (ie. toggle between apps, toggle between documents, back one word, back one sentence, skip word, skip sentence). Then perhaps a few "reading modes" (ie. forward letter by letter, forward word by word, forward sentence by sentence). "reading operations" could obviously be remapped to have different meanings depending on the context of which application you're using (ie. get GPS from GPS app, get time from watch app, get date from calendar app).
Alot of that is obviously pie in the sky thinking. But the only component that I think is going to be tough to find as small as I want (for the prototype) is going to be the solenoids.
But then again they're simple enough to create from scratch I may end up trying that.
Prior art is covered since the early 1950's