Thank you for your comment. Software development, for which I am intimately familiar with, depends on a lot of factors. You have to design a product that is both functional, provides value, and appeals to the broadest spectrum of users. In doing so, trade offs are often necessary. Now, let's take a specific example and instead of an app, make it a hardware device like a printer. There are several varieties of operating systems, Windows, Linux, mac OS,etc. In addition to them, there are subsets, flavors or versions of the operating system as well. You as a developer of driver software have to determine if you wish to produce a driver for that particular operating system and version and which not to. Additionally. This adds complexity to the cost of the device. Unless you know that the hardware is uniform and the OS remains the same without modification, the developer must make sacrifices. There are things code factory should address with a minor update, like better market access, and they need to be more responsive to their customers, but until Google standardizes what, in the name of open source, they will permit third party developers to alter the underlying Android component, or leave out of their apps use of built-in features of the OS, we will have this problem. OK, I paid one hundred dollars for my product, on top of signing a two year contract for a subsidized price for a phone, I expect it to work. I get that, I agree. That is why it behooves you to do a little research before you jump in. Many of the problems experienced have been well documented and would have been apparent with just a little research. Sometimes, our expectations can only be met by producing a specialized version for each phone. That could double and even triple the cost. Ask yourself this, if MA worked as you expected but you had to spend $300 for it, would you or would you find a less expensive alternative? Should Code Factory not have their feet held to the fire, you bet. Should they receive the brunt of the blame, no. The standard excuse to blame it on the assistive technology rings hollow to me if you could have adapted standardized practices in the first place, making it easier for assistive technology vendors to keep up.

though I am not making excuses for Mobile Accessibility's failings and Code Factory's response, I hope this gives you all a better understanding of the complexities in designing an application for our use.

Dusty



On 11/11/2011 4:36 AM, Jarrod Jicha wrote:

THANK YOU!!! THANK YOU!!! THANK YOU!!! A-MEN!!! A-MEN! Dusty TagueACTUALLY HAS A CLUE! THANKS FOR SAYING THIS!!!!!!!!!! this is one thing that blind persons tend to forget. in android you are not dealing with standards across all phones like you do with apple. this is not something that CF can predict, or make work all the time. if people keep blaming CF for things they can't control, I wouldn't be supprised if they make us wait for an update. I just got a new phone myself, and it is a lot differant than my other one was. I had a sanyo zio, and it had an answer call button, and the power button worked as a hang up button on calls. now my new one, the transform ultra doesn't have the answer call button, and is running on gingerbread 2.3 and not 2.2 what ever it was called. anyway, things are much differant for answering calls, and hanging up. on this one I have found that I have to open the keyboard, and press right arow once, then the select button. this works **ALL THE TIME** I could turn on a feature called power button ends calls, but that one seems to leave the screen on when you are on a call, and you press things with your face. smile.

my whole point in this is that people need to take a breath, count to 10 and quit blaming CF for androids problems. either learn to work around them like the rest of us do, or go buy an i-phone, and suffer some of its faults.

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Dusty Tague
*Sent:* Thursday, November 10, 2011 2:37 PM
*To:* dan greene
*Cc:* 'Mobile Accessibility Android Users List'
*Subject:* Re: [MA] Answering A Call

It is not just code factory at fault, it is android for allowing fragmentation to occur making this a problem. I think I can honestly say that for some the simplicity and continuity makes the iPhone a better purchase. The reason I said generally is that the manufacturers aren't always consistent in labeling buttons and placing them in the same location, but I have found that there are few exceptions to this and differ according to the particular app. That is the problem with a one size fits all approach on a fragmented platform. It is a shame that t-mobile doesn't offer the iPhone. You could try the sidekick 4g, or the lg my touch q, check the keyboard first to make sure, and see if that would be a better phone.




On 11/10/2011 12:22 PM, dan greene wrote:

That may be true, but on the MyTouch 4G Slide, with MA running, sometimes the trackpad works for arrowing down and to the side, and sometimes it does not.

And, now forgive me if this sounds argumentative, it should not take me 3 or more gestures to hang up the phone.

And, again being argumentative, why should there be one procedure for answering/disconnecting the phone when it's waking up, and another when the phone is awake as the call comes in?

And, finally, if the phone is still against my ear when I try to hang up, it's usually displaying a different screen than if I move it away from my ear--something CF seems to forget to tell users in its, so-called, manual.

I laughed out loud when I read your sentence that contained the words "generally works".

Generally works???? I just spent over $300 for a phone, and CF wants over another $100 for this software. Seems to me that things should be a bit better than "generally works".

And CF should support its users better, instead of canned responses to their problem reports.

I certainly mean no disrespect to you, I thank you for responding, but I've spent almost a week trying to help my wife learn this new phone, and the inconsistency of operations, and the absolute lack of support from CF, is unbelievable.

Cheers

Dan G

    ------------------------------------------------------------------------

    *From:*[email protected]
    <mailto:[email protected]>
    [mailto:[email protected]] *On Behalf Of *Dusty Tague
    *Sent:* Thursday, November 10, 2011 11:03 AM
    *To:* Mobile Accessibility Android Users List
    *Cc:* Steve Cook
    *Subject:* Re: [MA] Answering A Call

    Dan, if you can answer a call in system screens, you can hang up,
    either arrow down once and to the right once and you should be on
    the correct button.  Another approach, also when using system call
    screens is to tap the screen to the right of where you tap to
    answer, not on the right side of the screen but more to the left
    side of middle.
      Both these approaches generally work on most phones regardless
    of manufacture as long as they have physical navigation controls.

    On 11/10/2011 9:05 AM, Steve Cook wrote:

    Thanks for this information Dan.

    Steve Cook

    Assistive Technology Consultant

    SC Commission for the Blind

    1430 Confederate Avenue

    Columbia, SC 29201

    Office: (803) 898-8788

    Fax: (803) 898-8882

    E-Mail:[email protected]  <mailto:[email protected]>

    -----Original Message-----

    From:[email protected]  
<mailto:[email protected]>  
[mailto:[email protected]] On Behalf [email protected]  
<mailto:[email protected]>

    Sent: Thursday, November 10, 2011 10:14 AM

    To: Mobile Accessibility Android Users List

    Subject: Re: [MA] Answering A Call

    Hi Steve,

    I have similar problems with the My Touch 4G Slide.

    When your phone is awake as a call comes in, there doesn't seem to be any 
way to answer the call using MA.

    the swipe up doesn't work, just increases the ringer volume, and, like you, 
the volume keys just silence the ringer.

    I haven't tried answering one call, while on another--the manual says just 
a swipe up will answer,  I tend to doubt that now.

    You can try using the system call screen, (it's selected by a checkbox in 
the MA settings/advanced dialog box) but I found that option even worse.

    With that screen enabled, I can answer the call, but I can't hang them up.

    It's just another annoyance to add to the list of things that aren't right 
with the MA application-- at least on the My Touch 4G Slide.

    Cheers

    Dan G

        -----Original Message-----

        From: Steve Cook [mailto:[email protected]]

        Sent: Thursday, November 10, 2011 07:37 AM

        To: 'Mobile Accessibility Android Users List'

        Subject: [MA] Answering A Call

        Hi All,

        I can make a phone call with my Android HTC EVO using MA.  My question 
How do you answer a call when receding one?  I have the using volume buttons 
checked to answer and hang up the call.  When pressing either of these keys, it 
just silences the phone.  Also, when the phone is in the lock position, I can 
answer the call by just moving my finger up the screen.  My problem comes when 
I am within MA and receive the call that I can't figure out how to answer the 
phone.  Thanks in advance for your help and I hope this is clear.

        Steve Cook

        October is National Employment Disability Awareness Month.

    _______________________________________________

    ma_mailing mailing list

    [email protected]  <mailto:[email protected]>

    http://list.codefactory.cat/mailman/listinfo/codefactory.cat.ma_mailing

    October is National Employment Disability Awareness Month.




    _______________________________________________

    ma_mailing mailing list

    [email protected]  <mailto:[email protected]>

    http://list.codefactory.cat/mailman/listinfo/codefactory.cat.ma_mailing

_______________________________________________
ma_mailing mailing list
[email protected]
http://list.codefactory.cat/mailman/listinfo/codefactory.cat.ma_mailing

Reply via email to