XPost: comp.mobile.android   
   From: nospam@nospam.invalid   
      
   In article , pyotr   
   filipivich  wrote:   
      
   > >> >> With my current Android phone, which is one of those keypadless   
   > >> >> wonders, it took me two weeks to discover how to answer it when it   
   > >> >> rang.   
   > >> >   
   > >> >the answer button on the screen was not obvious enough??   
   > >>   
   > >>  You missed the point that these "smart phones" will help you so   
   > >> much, getting in the way of what it is you are trying to do.   
   > >   
   > >nonsense. helping do something does not get in the way.   
   >   
   >  I take it you've never had children, apprentices, or New Guys help   
   > you.   
   >  Nor have you used any other OS than Windows Ten.   
      
   you'd be wrong and kids have *no* problem figuring things out. they're   
   usually the ones explaining it to mom&dad.   
      
   > >>  Think of it as when you go into the room to answer the phone,   
   > >> opening the door causes the phone to be moved into a closet.   
   > >   
   > >that makes no sense.   
   >   
   >  Of course.  But smart phones do something "like that" all the   
   > time.   
      
   no they definitely don't.   
      
   > >>  Naturally, that image doesn't work if you have no experience with   
   > >> telephones which sit on a desk or table, connected by a wire through   
   > >> the wall to the central switchboard.   
   > >   
   > >i have plenty of experience with all sorts of phones.   
   >   
   >  And yet you seem to believe that the programmers never change   
   > anything in an upgrade which so "improves the smart phone experience"   
   > to the point you have to relearn how it works.   
      
   not anything significant, certainly not for answering the phone.   
      
   3 out of 3 completely wrong. keep up the good work.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)