So these are my aims for todays session-from slide-beer from the disco-opportunity to ask questions – but feel fre to shout out whenever.
Rough outline of the timings – but I’ve not actually practiced so we’ll see how we go.Someone shout if I’ve been talking on for hours.Live coding is a bit of an experiment.Feel free to hang arund after for a chat and with the wider group who organise JLUGS – Mat/Liam etc
First a confession – this group is meant to be for JVM language users-But actually Android apps don’t run on the Java VM – they actually run on an open source VM called Dalvik.Dalvik is an alternative acrhitecture to the JVM.Good at runningn on machines with low memory and no/little swap space.Oracle are not big fans
Outline of the android system architectureAndroid based on linux kernel 3 in latest, was 2.6 I thinkBunch of supported libraries provided by external providers – SSL etcAndroid runtime libs in C and Dalvik VMApp framework – provided as part of Android – full API docs available etcApplications sit on top of that stack – many provided by Google (not open source)And that’s what we can build too!
This compiled APK runs against the Android runtime libraries which are on devices.When building an application we use the Android SDK (ADK) which includes those runtime libraries and a bunch of tools.
Android is secure by design from the start – hard to build malware / bad apps.Applications execute within a sandboxFrom slide
-Android UI is big - and really a whole talk on it's own--All Android UI components are in a hierarchy of View and ViewGroup objectsprovded by the SDK--Android provides a lot of these for you - but you can also create your own.----Can define UI in code - but much easier to do so in XML
This is an example of a declaritive UI layout – making use of android provided UI elements.However this is not a talk about Android Uis….
I’m not a UI guy- the tools help – but get a real designer That said – a UI is important – so I’ll leave learning the UI tools as an exercise for you guys.Along with the UI you’re going to need some resources
Seperation of concerns in terms of designAllows app to provide multiple types of resources to suit various devices.
Components are the building blocks of all Android applications – this is where the bulk of the java code lives.
Manifest pulls it all together – this file is critical.This is where you can specify the requirements your app has from the device – Play picks these up.-Never assume these exist – can check in code if they really do.
Focus of rest of talk.Components are the building blocks of all Android applications.-Nothing happens without the core components – no matter how good your UI layouts are Compoonent = a point through which the system (not necessarily auser) can interact with your app
BR is the simplest component – but critical to a useful system
Intents are the basis of a late binding event driven system – REALLY IMPORTANT IN ANDROIDFor Activities and Services: Intent defines: action to perform (e.g. view, send...) andcan specify URI to data (to perform on) - and other context the component may need.-Return values can also be sent as Intents.For BRec's: Intent = the announcement being broadcast e.g. "battery is low"-Content Provider:---Not activated by Intent---Activated when targeted by request from ContentResolver (abstraction layer - provides security)
So that’s the brief overview – Now into the detail…
3 nested loops:onCreate - being created - Setup global state (define layout)onStart - about to become visible - register recieversetc that affect UIonResume - has become visible - fast codeonPause - losing focus - will get here a lot - only guaranteed closing state (if OS is in kill mode) so write crucial data hereonStop - lost focus, not visible - unregister receivers etconDestroy - about to go - clean up
Saving state:-additional callback onSaveInstanceState()---Store key value pairs putXXX---Most widgets do this for you. Nice.-Get this back in onCreate() or onRestoreInstanceState()
Data = URI
Data = URI
Data = URI
Data = URI
Introduction to Android Development
Introduction to Android
Goals of this session
• Give an overview of the Android Ecosystem
• Explain the core components of an Android
• Drink beer
• Create a simple working Android Application
• Drink more beer
Order of Service
Introduction to Android Development (45mins)
Live Coding – (45mins - or until it compiles)
Android VM != JVM
Android Apps are:
• Written in java (mostly) • Compiled to bytecode
• Converted to .dex files • Run on the Dalvik VM
What’s inside an App
• Compiled Java source code
• Library dependencies e.g. MIME type lib
• XML Files – UI layouts, fragments etc.
• Images, sounds, videos etc.
• Each App is assigned a user in Android linux
• Each linux process has it’s own VM
• Each Application runs in 1 process.
• Applications can request permissions to
system resources etc. - but user must agree.
• Additional files and static content that your
• Layouts for different types of devices and
• Images for different screen sizes and densities
• Referenced by unique ID within code
• Allow easy localization
• Defines application components
• Identifies required permissions
• Defines required API level
• Definers hardware/software features required
• API libs to link against (e.g. maps API)
• Components not in the manifest aren’t usable
Intro to Activities
• Single screen with UI
• Multiple activities exist in same app
• Activities work together but each is stand
• Any app can trigger any activity in any app (if
• More on that later…
Intro to Services
• Services generally run in the background
• Perform work that a user isn’t aware of
• Multiple components can make use of a
• Example: GPS service, mp3 playing
Intro to Content Providers
• Mechanism to allow apps to interact with data
• Create, Query, Store, Update
• Can store data in multiple ways File System, DB,
network storage, or anywhere else the App can
• Apps can query any Content Provider if they have
Intro to Broadcast Receivers
• A listener for system wide events
• No UI component
• Tend to be lightweight and do little work
• Example: Low battery handler
Intro to Intents
• Intent binds components to each other at
runtime (e.g. Event mechanism)
• Explicit Intent = message to activate specific
component by name
• Implicit Intent = message to activate type of
• Components define which Intent Types they
pick up with Intent Filters
• Any app can start any other apps component e.g.
use the camera app activity to capture pictures
– Don't need that code in your app
– Components run in the process of the holder app (e.g.
camera take pic activity runs under camera process).
– Android apps don't have single entry point (main
• Activating a component in another app is not
allowed by system permissions - so use Intent.
• Activity: pass Intent to startActivity(…)
startActivityForResult() - gets a result
• Service: pass Intent to startService() or
bindService() if running already
• Broadcast: pass Intent to sendBroadcast(),
• Content: call query() on a ContentResolver
• One main per app – identified by Intent type
• Each new Activity pushes previous to back
• Back button destroys current and pops
• Callback methods are how the system
interacts with Activities – can be triggered by
Activities – States
• Resumed/Running: up front and has focus
• Paused: Another Activity is on top of this one but this is still visible.
• Stopped: Backgrounded - still alive, not
attached to window manager
• The OS can kill activities without focus – but
will restart if possible.
Activities – Starting
• Explicit Intent to start Activity:
Intent intent = new Intent(this, SignInActivity.class);
• Implicit Intent to start Activity:
Intent intent = new Intent(Intent.ACTION_SEND);
• Need a result?
– Call startActivityForResult() then implement onActivityResult() callback
– Get the result in an Intent
Activities - Stopping
• Call finish()
• To shutdown an activity you start call
finishActivity(…) – but Android will do this for you.
• Saving State: onSaveInstanceState()
• Rotating the screen destroys current Activity so good way to test restore logic.
Activities - Advanced
– Sub Activity with own lifecycle
– Can be an invisible worker
• Loaders (3.0 +)
– Async pull data into Activity Views
• Long running operations - no UI.
– e.g. play music
• Service can run forever, but should know how to
• Started service = runs in background - does it's
own thing until it stops
• Bound service = allows interaction/feedback.
Destroyed when all components unbind.
• Determine type of Activity by implementing
Services - Callbacks
– which returns IBinder = the defined interface for
Services – Start/Stop
• bindService (Intent service, ServiceConnection
conn, int flags)
• System destroys bound service – when clients
• Note that system can kill service without warning - but
will restart it
Services - Manifest
• Must declare all services in your
application's manifest file.
• Supports IntentFilters and permissions.
Services - Threads
• Services use the Main UI thread – this is bad.
• Your service should create threads it needs to
– If you want to handle multiple thread
simultaneously you need to manage this here.
– You need to manage stopping the thread too
• Alternative is to extend IntentService – offers
worker per request – one at a time.
Services - IntentService
• Creates a default worker thread that executes all intents
delivered to onStartCommand() separate from your
application's main thread.
Creates a work queue that passes one intent at a time to
your onHandleIntent() implementation, so you never have
to worry about multi-threading.
Stops the service after all start requests have been
handled, so you never have to call stopSelf().
Provides default implementation of onBind() that returns
Provides a default implementation of onStartCommand()
that sends the intent to the work queue and then to your
Services – User Comms
• Services can communicate with the user in a limited
• Once running, a service can notify the user of events
using Toast Notifications or Status Bar Notifications.
• Toast notification is a message that appears on the
surface of the current window for a moment then
• Status bar notification provides an icon in the status
bar with a message, which the user can select in order
to take an action (such as start an activity).
• Component that responds to system-wide
• Many broadcasts originate from the system
• Register for intents via Manifest
• Meant to do very little work
• Receiving a broadcast involves:
– Registering receiver in Manifest or dynamically
• onReceive(Context, Intent)
• Normal broadcasts: Context.sendBroadcast()
– All receivers of the broadcast are run in an undefined
order, often at the same time.
• Ordered broadcasts:
– Delivered to one receiver at a time.
– Each receiver executes in turn, and can propagate a
result to the next receiver, or abort the broadcast so
that it won't be passed to other receivers. Similar to
Filters in JEE
• Manage secure access to data - across process
– Don't need one if you're just providing data to
– Use ContentResolver to access data in a
• -Android includes ContentProviders for
contacts, audio, video, images etc
• Data can be file (video etc) or Structured (tabular)
• Data is provided as tables (similar to relational dbs)
with primary keys (if needed)
• Content is referenced using a URI scheme
– e.g. content://user_dictionary/words
– Need to ask for permission to use a provider - this is done
in the manifest
• Define a query to perform against the URI.
– Returns a Cursor
– Cursor can be wrapped in a CursorAdaptor and bound to a
Intent and IntentFilter
• Activities, Services and Broadcast receivers are activated through
• Intent is a passive bundle of information. OS figures out how to get
it to the correct place.
• Intent is:
Optional component name
Action (e.g. ACTION_BATTERY_LOW) - you can invent your own
Data - URI of data and MIME type
Category - type of Intent (e.g. CATEGORY_LAUNCHER)
Extras - key/value pairs
Flags - how to deal with the intent
• Explicit Intent = named
• Implicit Intent = category of intents
Intent and IntentFilter
• IntentFilter tells the system which type of
Intent a component can handle
• Component can specify multiple filters
• Filter has fields that parallel the action, data,
and category fields of an Intent object
• Intent must match all 3 fields to be delivered
– Note that Intent may not specify a field…
• Action: Intent action must match at least one Filter
action. Intent can leave action blank and match
• Category: Every category in the Intent object must
match a category in the filter. Filter can list additional
categories, but it cannot omit any that are in the
– android.intent.category.DEFAULT must be implimented
– No data = match
– More complex rules for data matching if specified
• Multiple filter match: Ask the user
Processes and Threads
• One process per app. One Main thread is created
for the App process – this talks to the UI aka
• General Rules:
– Do not block the UI thread
– Do not access the Android UI toolkit from outside the
• Workarounds: Create own threads and use
• AsyncTask allows you to perform asynchronous
work on your user interface. It performs the
blocking operations in a worker thread and then
publishes the results on the UI thread, without
requiring you to handle threads and/or handlers
• Subclass AsyncTask and implement:
– onPreExecute, onPostExecute(), onProgressUpdate()
• Run Task from UIThread by calling execute()
• Android Platform + SDK
• Android Developer Tools (ADT) for Eclipse
• Android Studio - Based on IntelliJ IDEA
• Currently in Early Access release
• Uses Gradle
• Emulators and Hardware debugging