In early 2012 I had the opportunity to explore Android development as related to industrial controls for Automation Solutions.  I immediately found the android developers website at google, but the dizzying array of options and terminology left my head spinning.  I wanted to get the information I needed fast without getting bogged down.  There are a couple ways to get across the techno-chasm, build a bridge using the tools at hand or go to school.  Because I am a techno explorere, I took the former.    This blog helps me unwind the material I’ve collected and, with luck, will be a benefit to future explorers.

Why is it so hard?  Cracking into Android world is no harder than any other.  It is largely a matter of getting into the “Android developer’s” head.    When I did development on the Palm Pilot, lo those many years ago, I faced the same learning challenge.  Same with Flash, and Java.  Learn their terminology.  Learn the framework.  Create a few experimental applications that get you into the tech, but not so much you lose your way and fail.  The key here is to take a bunch of baby steps so you never need a great leap into a techno black hole.

When I did development on the Palm Pilot, lo those many years ago, I faced the same learning challenge.  Same with Flash, and Java.

What about the literature?  Since I am a late-comer to the Android environment, there many books out there.  I took all the useful books I could find from the main branch of the Portland public library.

• Android development for dummies
• Developers guide to Android Development

 

What they do:   Install developer tools,  Create and run  a “hello world” app that shows how the simulator and IDE work together.  Next they talk about UI basics.  How to put stuff on a screen or Start talking about UI basics, yadda yadda yadda.

What I am going to do.  Not much different.  The projects should be multifaceted meaning they will implement a series of experimental applications.  Only the first is a throw-away. All others should be heading toward what a commercial application would need in terms of functionality and look-and-feel.

Uncover Android’s UI elements without getting overwhelmed.  Get in the habit of writing programs the Android way.   For example, use Strings.xml so translation from one language to another becomes nothing more than a linguistic exercise.  I will use XML based screen layouts, themes  and inline subclasses for button responses.

Project 1:  Hello World Application

• Hello World
• Add “About” screen
• Add “preferences” screen (save the theme)
• Add context menu

Project 2:  Save Data Locally

Project 3:  Background Services

Project 4:  getting data from external sources

Project 5:  game-time – super labrynth

Project 6:  Dear Abbey, jumble daily crossword puzzle app.