Scribd
Upload
13 views

Chapter 2 - SDK Install and Initial Setup

Uploaded by

Phạm Thanh Phúc - B20DCCN512
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
13 views

Chapter 2 - SDK Install and Initial Setup

Uploaded by

Phạm Thanh Phúc - B20DCCN512
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 34

CHAPTER 2.

SDK INSTALL AND INITIAL


SETUP
SDK and initial setup: Outline

Today:
 How to setup a machine to start developing Android
applications
 An overview of an Android project
 Some useful tools
 Your first Android application
• Maybe on a real device!

2
Two options

Historically Android development was in Eclipse


Download the SDK
Install the Android plugin

Now there is Android Studio


You still have to download the SDK
Customized environment

3
Which one?

For the class, it’s the same

If you already use and love Eclipse, go with it

You might see examples done in both platforms


You can always import an Eclipse project into Android
Studio
The inverse is difficult

4
Android Studio

5
Where and how to get it

Go to http://developer.android.com/sdk/installing/studio.html

Download Android Studio


and the SDK

Install it and you’re done!

6
Basic requirements

How to develop Android applications?


Linux/Mac OS X/Windows? Doesn’t matter
A real device is not mandatory

Code your application in the IDE


Test it with the emulator
Deploy it on a real device

7
SDK tools

 Android tool

 Used to get APIs


and add-ons

 You can also start it


from Android Studio

8
Your first Android application

Go to File > New Project

9
Testing on the emulator

Select “Launch Emulator”

10
Creating an emulator

 Can configure several


options

 You can create as many


as you want

11
Did everything went fine?

 Test in on the emulator

 You should see something


similar to this

12
Hello world, Android!

Anatomy of an application
Activity: what is started
View: what is seen
Intent: how to communicate with others

Mix of XML and Java


Generally XML for layouts
Java for the app logic

13
Application structure

Even the simplest application


has a lot of files
Some are autogenerated
Each project contains
Activities
Layouts
XML files
AndroidManifest.xml

14
build

Autogenerated files
No need to modify them
Some are autogenerated
Each project contains
Activities
Layouts
XML files
AndroidManifest.xml

15
src

All the code of your application


The java folder contains… the
java code!
Inside res there are a lot of
resources
Images
Layouts
Xml files
AndroidManifest.xml
16
AndroidManifest.xml

Mandatory file for every


application
Contains:
Application declaration
Permissions
Intent filters
Targets

17
How to test

Via an AVD
 Fast, possible to have different resolutions, APIs
 Not a real device
On a real device
 You get exactly what is deployed
 Must own a real device
So?
 Test in on AVDs.
 When you feel that the application is ready, go with a real device

18
How to deploy

Android applications must be signed before installing


them on a real device

 You need a key for this


 and you can generate one
 from the menu.

19
ECLIPSE
SDK and initial setup: 3 step setup

 Download Android SDK for your platform:


http://developer.android.com/sdk/index.html
 Execute (and then select the Android API version):
android-sdk-xxx/tools/android
 Install the ADT plugin for Eclipse:
http://www.eclipse.org/downloads/
https://dl-ssl.google.com/android/eclipse

21
INSIDE THE SDK
ADT PLUGIN FOR ECLIPSE

 Useful to run applications via Eclipse, highly reccomended


 Go to http://developer.android.com/sdk/eclipse-adt.html
 Pick the repository (actually https://dl-ssl.google.com/android/eclipse/)
 Add a repository in Eclipse and download the “Developers Tools”
 This will make a virtual bridge between eclipse and the SDK
CREATE A PROJECT

 Create it under Eclipse


 Assign an SDK target
 Choose an application name
 Choose a package name
 Create an activity and assign a name
 Run it to test that everything is ok
CREATE AN AVD

 AVD means Android Virtual Device


 Test the application before running it on a device
 Multiple APIs → Multiple targets
 Makes it faster (and cheap) to test application on
different configurations/resolutions/storage
PROJECT CONTENTS

 Project name
PROJECT CONTENTS

 Project name
 Src folder with java files
PROJECT CONTENTS

 Project name
 Src folder with java files
 Auto-generated files
PROJECT CONTENTS

 Project name
 Src folder with java files
 Auto-generated files
 Android's base files
PROJECT CONTENTS

 Project name
 Src folder with java files
 Auto-generated files
 Android's base files

 Compiled files
PROJECT CONTENTS

 Project name
 Src folder with java files
 Auto-generated files
 Android's base files

 Compiled files

 Resources files
PROJECT CONTENTS

 Project name
 Src folder with java files
 Auto-generated files
 Android's base files

 Compiled files

 Resources files
 Android Manifest
HOW TO DEPLOY

 Android applications must be signed before they can be installed on a device


 Eclipse can sign applications
 Debug mode, just to test it on your device
 Release mode, when it's ready for other users
SIGNING IN RELEASE MODE

 Eclipse has a tool called Export Wizard


 File > Export
 Export Android Application
 Select your key and preferences
 Application is compiled, signed and aligned, ready to be deployed
 Keep your private key safe
 Use a strong password
 Don't lend it to anyone

You might also like