4 ms·

I am part of the team who created the app and api. Many blind users use the voice over feature built into ios as @rgoodwintx mentioned.

by khebbie 12y ago

dntrkv 12y ago
One problem that I see (you guys might already address this) but if I'm a helper and I get a call from a blind person and I have just a couple minutes to help but the blind person needs 10 minutes of help it would be inefficient to connect me with them. One way to solve this would be for the blind to select a time range of how much help they need (1 minute, 5 minutes, 10 minutes, etc...) and then when it calls the helper it will show how much help is needed, so they can either decline or go into the call knowing how long they will be busy for. Also you may be able to introduce pricing in this way, where anything under 5 minutes is free, but over 5 minutes you charge however much per minute and then split the cost with the helper.
- khebbie 12y ago
  We didn't think about that but will take it into consideration. The app will probably stay free as that is the whole base of this. But the expected timespan is very usable. Thank you.
27182818284 12y ago
What made you choose iOS first over Android? (Was it an arbitrary choice or one driven by data that more iOS users would be on board with this sort of project than Android users? Maybe something simpler like the developers had more iOS experience?)
ilyaeck 12y ago
Great undertaking, guys! I am from Robin Labs, we create voice assistants and would like to build one for the blind (Siri-style, but one that is really eyes-free). To do that, we need somebody who understands the target audience and their use cases better than we do. Maybe we could team up and make a difference. If that sounds interesting, please ping me at ilya AT robinlabs DOT com.
- ilyaeck 12y ago
  We could potentially build your API into the Assistant for cases where the machine cannot help - them the user would summon a human.

I am part of the team who created the app and api. Many blind users use the voice over feature built into ios as @rgoodwintx mentioned.

by khebbie 12y ago

I am part of the team who created the app and api. Many blind users use the voice over feature built into ios as @rgoodwintx mentioned.

dntrkv 12y ago

One problem that I see (you guys might already address this) but if I'm a helper and I get a call from a blind person and I have just a couple minutes to help but the blind person needs 10 minutes of help it would be inefficient to connect me with them. One way to solve this would be for the blind to select a time range of how much help they need (1 minute, 5 minutes, 10 minutes, etc...) and then when it calls the helper it will show how much help is needed, so they can either decline or go into the call knowing how long they will be busy for. Also you may be able to introduce pricing in this way, where anything under 5 minutes is free, but over 5 minutes you charge however much per minute and then split the cost with the helper.

khebbie 12y ago
We didn't think about that but will take it into consideration. The app will probably stay free as that is the whole base of this. But the expected timespan is very usable. Thank you.

27182818284 12y ago

What made you choose iOS first over Android? (Was it an arbitrary choice or one driven by data that more iOS users would be on board with this sort of project than Android users? Maybe something simpler like the developers had more iOS experience?)

ilyaeck 12y ago

Great undertaking, guys! I am from Robin Labs, we create voice assistants and would like to build one for the blind (Siri-style, but one that is really eyes-free). To do that, we need somebody who understands the target audience and their use cases better than we do. Maybe we could team up and make a difference. If that sounds interesting, please ping me at ilya AT robinlabs DOT com.

ilyaeck 12y ago
We could potentially build your API into the Assistant for cases where the machine cannot help - them the user would summon a human.