Share HN: I wrote an app to help my paralyzed cousin type significantly faster.
chir.ag
chir.ag
This isn't a startup and I honestly don't want to treat it like a business. However, I do think it qualifies as a hack because of how it works. It uses Google Suggest in addition to a dictionary to try to guess the next word that the user is going to type. If you type WHERE, the next word is most probably going to be IS, THE, or DID. If you then select IS, the next word after WHERE IS will probably be THE or MY. KType uses this and a few such principles to make smarter, better guesses. It is not perfect but I intended to make it extremely smart and customized per user. When I was actively working on this, I had 100 ideas per day on how it could basically read the user's mind and suggest words and phrases most effectively.
My family and I looked at many existing systems for making typing easier but there wasn't anything out there so I decided to roll our own. As of right now, I don't know where to go with this because of my cousin's uncertain health condition. I would love to hear from medical and text hackers about developing this further.
Note: Currently I use Google Suggest localized for India so many of the suggestions may seem weird to non-Indian users. However, it's a simple change in URL to get localized suggestions for any country thanks to Google. Also, I wrote it for 1280x1024 resolution but it can be resized for most screen sizes.
Google "Social Entrepreneurship" for more details.
- Accept keyboard input. Some users might find it easier to press a key rather than use a mouse or even a touch screen. It would enable support for stuff like this: http://www.usm.edu/ids/tlc/images/hw-ikeys.jpg
- Feature a big "copy text" button so that the user might be able to use your service and paste said text somewhere else on the web.
It can let someone who is fully paralyzed, with just eye movement, type at a very good speed. And it works for less paralyzed people too (it has configurable modes).
I don't know why it's not more frequently used, but it should be - it's much better than most other typing software used in these cases.
Edit: I just noticed you listed it on the page.
Edit2: And I see everyone else told me that too.
"KType is not a text-entry system for average users like T9 and Dasher."
My cousin's child has severe Cerebral Palsy. He has a dedicated device[1] to help him interact.
Maybe you could include some ideas from these existing devices?
---
BTW, well done on your implementation.
---
I develop a mouse accelerator which makes moving the mouse a lot easier. When it is ready, I will post that onto HN. Your article has shown that the reception will be good.
It suits disabled people who have poor muscular control over the mouse.
------------
[1] MyTobii ::
http://www.inclusive.co.uk/cgibin/sh000001.cgi?REFPAGE=http%...
There are large bodies of text such as wikipedia and others that you can download, maybe you could use them to aid your prediction ?
It would also make the application work when offline.
Even if I make an app for iPhone/iTouch, most users can still access the web and make use of Google Suggest so the effort to go through 20GB of Wikipedia/DBPedia/Freebase data and implement my own intelligent search didn't seem worth it.
Also: Interesting that you laid out the letters simply in alphabetical order (as opposed to QWERTY, Dvorak, or anything else).
It shouldn't be too difficult to incorporate this into a webapp that lets the user type lots of text - sort of like the T9 mode on your cellphone. The original goal was to allow the user to type about 140 characters (SMS/Twitter) and hit a Submit button.
The reason for choosing alphabetical layout was to minimize mistyping due to unsteady hands. Three rows like a QWERTY etc. keyboard means when user is trying to hit a key in the middle row, they could accidentally hit a key above or below the desired key. In two row layout, this issue is minimized. Also notice the keys are in a piano-keyboard style layout with ample gap around each key, thus reducing the chances of error further.