Intro to Android Programming

Introduction to Android Programming 0 to “Hello World” in 60 minutes or less Silicon Valley China Wireless Group Peter van der Linden [email_address] Android Technology Evangelist Developer Community Technical Services Motorola Mobility

Content Moore’s Law and mobile devices Android Software Development Checklist Ingredients of an App GUI basics Getting into code Running your code Q&A These slides are online at: http://www.slideshare.net account: pvdl01

Moore’s Law and Mobile Devices “ the number of transistors on an IC doubles approx every two years” Electronics Magazine, 19 April 1965 It’s the law - trend has continued for 45 years, and keeps going Trend is predictive of cpu Hz, storage size & speed, power consumption, network speed, etc etc Partly self-fulfilling, as it guides hw roadmaps

Smart Phone Family Tree PDA cell phone smart phone tablet netbook laptop Moore’s Law Moore’s law Actual Family Tree

My Phone has 802.11 b/g/n Wifi 1 GHz CPU Moore’s Law This is not a toy. This is equivalent to a Windows XP PC 512 MB RAM bluetooth DVD quality video player Music quality audio USB port

My Droid X Phone ALSO has accelerometer Digital compass Moore’s Law Today’s Windows PCs don’t have these … HD video capture Voice phone with noise-canceling hw 8 MP camera Orientation sensors GPS receiver

Smart Phone Family Tree smart phone laptop Moore’s Law A more insightful way to think of it! = + more hw

Implications of HW capabilities Moore’s Law Expect the same characteristics as desktop apps Large and powerful API to choose from Development time and cost Plus need for great app graphics, icons, UI design The app sales channel problem is solved for you

2. Android Software Checklist Embedded software development expertise Java Desktop SE expertise (who has Java cert?) Eclipse IDE expertise XML expertise SQL database programming expertise Open GL programming expertise The more of these you have, the easier your learning curve will be

2. Android Software Checklist Who has programmed in Java? Who has used any IDE? That’s enough to get started!

The SDK tool chain 5. Java runtime SE ver 6 4. Eclipse 3.5 3. Eclipse ADT plug-in 2. Android SDK 1. Android Platform(s) Download 1,2,3, from developer.android.com 4 from Eclipse.org 5 from java.com

One stop shopping for Tools http:// developer.motorola.com/docstools/motodevstudio/download If you need to install Java runtime, it will tell you Versions for Windows, MacOS, Linux, 32 and 64 bit IDE for all Android on all platforms from all Manufacturers MOTODEV Studio

Compile time tools Java JRE Eclipse 3.5 Eclipse ADT plug-in Android SDK Your code lives in Eclipse Your code is compiled by the SDK The Eclipse ADT plugin helps your code work with the Android SDK The Android SDK contains the Android libraries and tools

Runtime Development Tools Eclipse 3.5 Android SDK Android Platform You tell Eclipse to run your code Eclipse tells the emulator in the Android SDK The emulator contains the Android platform libraries. Emulator is an app on your PC that emulates Android hw Or use a real Android device over USB connection Emu

3. Ingredients of an App Source code for every Android app has: Java “ glue” XML, icons Media, data files, etc AndroidManifest.xml describes the app overall, features used, version, etc

Create app in Eclipse, by File > New > Android … Ingredients of an App, II

These folders and files are created, to start you off Ingredients of an App, III Java “ glue” code XML, icons, etc Manifest.xml

Ingredients of an App, IV When you create a new app in Eclipse, you get: A complete set of files and folders, that form “Hello World”, Including A Java source file An XML file (defines layout of components on the screen) Some generated “glue” code to make XML names visible to Java Some icons An overall AndroidManifest.xml file describing the app to the Android system

4. GUI Basics Modern GUIs have common elements: Components (buttons, dialogs, progress bars, canvas, etc) Components are grouped and laid out by a layout manager LinearLayout Button TextView Press You can have text in a TextView Another Button

4. GUI Basics Modern GUIs have common elements: Components generate events from user input. You write & register callback routines to handle events Events are delivered to you on a UI thread (avoids the need for locking code in the GUI) Your code is called when needed public class MyActivity extends Activity implements OnClickListener { Button b= (Button) findViewById(R.id.pressme); b.setOnClickListener(this); . . . // Implement the OnClickListener callback public void onClick(View v) { // actions when the button is clicked }

GUI Basics Android follows the conventional model in most respects One exception: components and layout is in XML, not code Here’s what the XML looks like: <Button> some attributes=“values” </Button> Usually shortened to this: <Button some attributes=“values” /> So your source is going to include a bunch of XML files

GUI Basics Your source includes a bunch of XML files

Getting into Code Every screen in your app is an Activity object that you code Your code extends android.app.Activity Every Activity has An XML file defining the GUI objects on its screen A Java file defining how user interacts with those objects And entry points that are called for you at the right moments when something happens in the GUI (screen created, button pushed, etc)

Getting into Code, XML 1 An XML file defining the GUI objects on its screen General appearance: <?xml version= "1.0" encoding="utf-8"?> <LinearLayout … some attribute=“value” pairs … > <TextView … some attribute=“value” pairs … /> </LinearLayout>

Getting into Code, XML 2 An XML file defining the GUI objects on its screen/Activity Full details <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="fill_parent” > <TextView android:layout_width="fill_parent" android:layout_height="wrap_content" android:text="@string/hello” /> </LinearLayout>

Getting into Code, XML 3 Every View must have a value for android:layout_width and _height Tells layout manager how much room you want for the WIDTH and the HEIGHT of the component "fill_parent” magic word that says “greedy – as much as possible” "wrap_content” magic word that says “frugal – as little as possible” <TextView android:layout_width= "fill_parent" android:layout_height= "wrap_content" android:text= "@string/hello” />

Getting into Code, XML 3 You can look at the screen this XML defines, in MOTODEV Studio

Getting into Code, II The phases of an Activity (the code for each screen goes thru these steps). Create (runs in the event loop until something stops it) Stop There are finer divisions within the phases, but this is the template You create methods to override the methods where you want to do something. You want to override onCreate, and set up your GUI

Getting into Code, Activity 1 Java file defining interaction with GUI objects on screen General appearance: public class MainActivity extends android.app.Activity { /** Called when the activity is first created. */ public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); // glue code! } }

Getting into Code, Activity 2 Java file defining interaction with GUI objects on screen Full details package com.motorola.hello2; import android.app.Activity; import android.os.Bundle; public class MainActivity extends Activity { /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); } }

Getting into Code, Glue The glue code is generated for you automatically Makes XML names in res folder, appear in Java namespace! This shows the convention for getting hold of layout files under yourProject/res/layout setContentView( R.layout.main ); // says “use layout in file res/layout/main.xml”

Getting into Code, Glue 2 The glue code is generated for you Makes XML names in res folder, visible in Java namespace! Create an ID name for an XML element with this attribute In Java, get hold of that XML-declared TextView by: In XML, get hold of that XML-declared TextView by: TextView tv = (TextView) findViewById( R.id.myTV ); <TextView android:id="@+id/myTV " <Button android:layout_below= ”@id/myTV "

Getting into Manifest AndroidManifest.xml – describes your app to the system < ?xml version= "1.0" encoding="utf-8"?> <manifest xmlns:android= "http://schemas.android.com/apk/res/android" package= "com.motorola.hello2" android:versionCode= "1" android:versionName= "1.0"> <application android:icon= "@drawable/icon" android:label="@string/app_name"> <activity android:name= ".MainActivity" android:label= "@string/app_name"> <intent-filter> <action android:name= "android.intent.action.MAIN" /> <category android:name= "android.intent.category.LAUNCHER" /> </intent-filter> </activity> </application> <uses-sdk android:minSdkVersion= "8" /> </manifest>

Running your code Test your code on a sw emulator, or on a handset via USB The sw emulator runs on your development system. It’s an app that emulates the hardware, and you load your test app onto it. Click “Run > Run as > Android Application” Live Demonstration of this

Follow-up developer.android.com – Reference documentation – Technical notes • developer.motorola.com – Technical Library – Product Specs – MOTODEV Studio – Discussion Boards – Blog posts – and more …

Q & A Where to find more information: http://developer.motorola.com One stop shopping, with links to many other useful places One stop Tools and SDK download Tools that work for all Android devices from all manufacturers.

Apache 2 license Copyright (c) 2007-2010 by the Android Open Source Project Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Copyright (c) 2010, Motorola, Inc. All rights reserved. - Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of the Motorola, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. BSD license

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. BSD license

Intro to Android Programming

More Related Content

What's hot (20)

Similar to Intro to Android Programming (20)

More from Peter van der Linden (8)

Intro to Android Programming