XPost: comp.mobile.android   
   From: this@ddress.is.invalid   
      
   Carlos E.R.  wrote:   
   > On 2017-04-13 10:24, Bob Henson wrote:   
   > > On 12/04/2017 11:23 pm, VanguardLH wrote:   
   > >   
   > >> Not knowing how to answer a call is just whining about being   
   > >> inexperienced with whatever app is used to accept a call.   
   > >   
   > > Not if that information is not available anywhere - it isn't whining,   
   > > it's a legitimate complaint about stupid design. There is no point   
   > > saying "buy a different phone" either - there is no way one can allow   
   > > for stupid design before buying the phone. By the time you have got it,   
   > > it's too late. My other phone dialling "bête noire" (and many others,   
   > > judging by the online complaints) is the contact interface on my phone   
   > > that will not find a partial number out of several hundred numbers in   
   > > the list - similar stupidity on the part of the designers.   
   >   
   > The design is correct. You have to slide the button instead of pressing   
   > it, because you can easily press the button accidentally, even inside   
   > your pocket. It is rare to slide the button accidentally.   
      
     Nope, the design is not "correct", as many have said, it's *stupid*.   
      
     Any 9 dollar 'dumb' phone tells you what to do when it rings, but a   
   100-900 dollar smart-phone can't be bothered to do the same and that's   
   "correct design"!?   
      
   > What is incorrect is the absence of instruction booklet; and when it   
   > does exist, it doesn't explain these things, that are unique to touch   
   > screen phones.   
      
     The absence of (real) documentation is yet another problem. But if the   
   UI design is done well, there's less need for documentation.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)