XPost: comp.mobile.android   
   From: nospam@nospam.invalid   
      
   In article , Arlen Holder   
    wrote:   
      
   >   
   > > Normally, I then develop an app...   
   >   
   > I admit I've never written an Android app in my life!   
   >   
   > I haven't even coded in decades.   
   >   
   > Some day I will write a tutorial for a "hello world" Android app.   
      
   don't.   
      
   plenty of people have already done so, including google.   
      
   > One thing I'd like to write is a camera app that does what I want.   
   >   
   > I just finished replacing a clutch and I documented every step with   
   > pictures, and the damn camera apps always fight me when working on a car in   
   > less than ideal situations.   
   >   
   > The damn front camera goes on too easily, and the settings don't get   
   > remembered and the camera has to work from a sound or single tap with   
   > gloves or a button.   
   >   
   > In fact, I'd make a camera app that did only one thing and one thing only.   
   > Take pictures.   
   >   
   > If there are settings to be changed, you'd have to punch a lot of buttons,   
   > on purpose, so that they don't get changed accidentally. It would be   
   > optimized to take the damn picture, and nothing else.   
   >   
   > If you did unlock and then change settings, they'd be PERMANENT. My damn   
   > camera app keeps resetting to its stupid (for me) defaults.   
   >   
   > Most of this doesn't matter in normal use, but under a car, with gloves, in   
   > poor lighting, with only one hand, in odd positions, all that starts to   
   > matter a lot.   
      
   user error.   
      
   if you can't figure out how to use existing camera apps (and there are   
   a lot of them), you certainly won't be able to figure out how to write   
   one.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)