Android Framework

3rd CodeAndroid Meetup – Understanding Android Basics and Development

Google, Temasek Tower, 8 Shenton Way25th May 20092 pm

CodeAndroid.org

• Android Developer/User Group

• Grassroots effort by developers

• Promote Android development around this region

CodeAndroid.org

Special thanks to

Google Singapore for the space and keeping us well replenished!

HTC Singapore for the goodie bags! (Given out at end of session Q&A)

Today’s Agenda

1. Android Frame"Works" – What's the importance and how to use them? - by Jerry Lim and Aaron Chan

2. Intents, Intent Filters, Broadcast Receivers- by Muh Hon Cheng

3. Test Driven Development on Android, Part 1 - Building Blocks of TDD - by Wade Mealing

4. Bluetooth-enabled apps using NDK 1.0 - for non-rooted phones - by Stephan February

5. Quiz (and goodie bag time!)

6. Network and chitchat

7. Home sweet home

Android Frame"Works" – What's the importance and how to use them?

- by Jerry Lim (SBS Next Bus) and Aaron Chan (MobileSorcery)

Android System Architecture

Application Layer

• Highest Layer in the Architecture

• Built-in standard applications-Phone Dialer-Email-Contacts-Web Browser-Android Market

Application Framework

The most important part of the framework are as follows:

• Activity Manager

• Resource Manager

• Location Manager

• Notification Manager

Process!=Application

Lifecycle of the rich and famous

• Each Activity has it own Lifecycle

• Application is one or more Activities

• Activity lifecycle is not tied to process

• Application can be “Alive” even when process has been killed

Life Cycle in an Android Activity


@override these methods in your Activity class, and Android will call them at the appropriate time

• onCreate(Bundle): This is called when the 1st Activity Startsup

• onStart(): This indicates the activity is about to display to the user

• onResume(): This is called when the activity can start interacting with the user


• onPause(): This runs when and activity about to go to the background

• onStop(): This is called when the activity is no longer visible to the user

• onDestroy(): This is call right before your activity is destroyed, if memory is tight onDestroy may never be called (The system will may terminate you process)

Join Us!• Website: http://www.codeandroid.org/

• Facebook: Google Android Developer/User Group Singapore

• Google Groups: http://groups.google.com/group/WeCodeAndroid

• IRC community: #codeandroid on irc.freenode.net (server)

• Twitter: http://www.twitter.com/codeandroid

Technology

Android Framework