CLAUDIO CHERUBINO: Hi everyone.

Welcome back to Google Developers Live.

My name is Claudio and I'm one of the engineers in the Google

Drive Developer relations team.

We get a lot of requests from you about what you want us to

talk about in Google Developers Live, but there is

one topic that most of you ask for, and that is how do I

write an Android app that uses Google Drive.

This is a very common feature request, and this is a very

important scenario for us.

So today I'm going to show you how you can write your first

Android application that uses Drive.

We also added this tutorial to the documentation on

developers.google.com/drive just today.

Probably two hours ago.

So you can watch this video, and if you need some guidance,

you missed some commands, you can always go back to our

documentation or you can watch this video again.

It's going to be recorded and you can watch it at any time.

So if we go to our documentation, as I said, in

the home page we have the list of five minute quick starts in

different languages.

The last one we added is Android.

We recently added Objective C. We're going to talk about it

in a future session of Google Developers Live.

But today we're going to talk about Android.

So if we click on this Android link here we will be brought

to the Android specific page.

It looks like all the other quickstarts.

So you might have seen this quickstart already.

We covered most of them on Google Developers Live.

The goal with these quickstarts is to have an

application in a few minutes, an application that integrates

with Drive.

As usual, being a quickstart, we tend to cut some corners.

So this is not going to be a perfect application.

We might not follow Android best practices today.

But still, with by following this you will have something

running and then you could always go back to it and make

it better, make it a production application.

If we look at our documentation there are five

steps to have this application running.

And the first one is very specific to Android.

So the first step is generating the signing

certificate fingerprint.

It's only required when writing an Android app.

Android has a unique authorization mechanism.

So it still uses Auth2, like we do with all other languages

in all other platforms.

But it requires the developers to register their package name

in signing certificates in the API's console.

So this is what we need to do as our first step.

If you're an Android developer you've

probably seen this already.

Whenever you want to publish an application on

play.google.com you have to sign your certificate with

your product.

This is the same thing and this is what we're going to do

and let me show how this works.

So the first thing to do is to generate the SHA1 fingerprint.

And you can do it by using a command

line tool called keytool.

There is the command line here in the Docs.

So if you're following instructions, as I'm doing,

you can just select it, and copy it, and execute it in

your shell.

So let me move to my shell.

I paste the command.

I'm using keytool to export my certificate

from the debug keystore.

This is important.

Every time you write an application in debug mode in

Eclipse it automatically generates a debug

keystore for you.

So we're going to use that debug keystore for our debug

application.

Whenever you want to move your application from debug to

production, you have to generate your own keys.

And this is well documented in the Android documentation.

If you're using the debug keystore, its default location

is inside a hidden folder in your home directory and the

file is going to be called debug.keystore.

When we ask keytool to export a certificate, we are asked to

type the keystore password.

If you're using the debug keystore password that is

automatically generated by Eclipse, the default password

is Android.

So I'm going to type Android and what I get is some

information about my key.

And what I need is the SHA1 fingerprint This line here.

We're going to use it in the second step.

So we're done with the first step.

So the first step is to recap exporting your signing

certificate SHA1.

And this is done using keytool.

Nothing special if you know about Android development.

So let's go back to the docs.

So we're done with the first one.

Of all those information what you need is the SHA1

certificate, the SHA1 fingerprint.

So we're going to keep him handy for later.

Second step is enabling the drive API

in the API's console.

This is the same thing you would do with any other

language in any other platform.

So we go to the API's console and we create a new project.

I'm going to click on create project.

My session is expired.

I'm going to reload the page and create a new project, and

then I have to enable the APIs I need.

To Drive API application I need to enable the drive API.

So I just click on Drive API, click activate, and that's it.

The drive API is now enabled.

Now I need to generate my credentials.

So to do that, I go to the API axis tab and

click on create [? Auth ?]

2.0 client ID.

When I do, I have a step by step wizard

that I have to follow.

In the first page I have to specify my product name, my

application name.

Let's say it's going to be Drive Quickstart.

You can also add a product logo and a homepage

URL if you have it.

If you don't just move on and click Next.

In the second page we have to select installed application

as the application type.

You can select different types of application.

One is a web application.

Otherwise a service account application we also covered

those in another session to Google Developers Live but

what we want is an installed application, which is an

application that is installed on the device.

So when I click on it I then have to choose whether I want

an Android app, IUS app, or any other kind of installed

application.

We're building an Android app so this

is going to be Android.

And when we do we have to specify the package name in

the signing certificate fingerprint.

This pair has to be unique and these uniquely identifies your

application, so that whenever an API call comes from an

application, Google will check if it matches this package

name and signing certificate.

So we have to be extra careful here.

We cannot use a package name and fingerprint pair we

already used.

So in our example the package name is going to be

com.example.drivequicksearch.

If you use these values you can basically copy and paste

the rest of the code from the documentation.

If you change this, obviously, you will have to change the

package name in your application.

The easiest way to get started with this quickstart, is to do

exactly as we do, which is even using the

same package names.

And obviously my package name will be the same as yours

because we will all use com.example.drivequickstart

but my signing certificate fingerprint, the SHA1 string

we generated, will be unique.

So the pair, package name, and SHA1 will be unique.

So we need the SHA1 and we can get it back from the terminal.

So let's go back here.

We need this SHA1 string we just generated.

We copy it from the terminal and we

paste it in the dialogue.

That's all it takes.

We can create client ID.

Now you can see in the API's console that we have our

credentials.

So we have a client ID.

We have an application type Android.

We have our package name specified and our certificate

fingerprint.

Since this is the debug certificate that Eclipse

already uses, when I will build my application using

Eclipse it will be automatically signed with this

same key, assuming that I'm running it in debug mode.

So if we go back to the dock, this is explained and we are

basically done with step two.

Step three is in Eclipse.

So we're going to create and configure an Android project

that uses the Drive API.

So I have Eclipse open here.

I have no other projects, so I'm going

to start from scratch.

I'm going to do file, new project, and select Android

application project.

Here I have to specify my application name.

In order for it to match what we put in the API's console

the application name has to be drivequickstart.

Remember if you change the application name to be your

own, you have to match it in the API's console.

So I'm going to type drivequickstart.

And as you can see the package name is automatically set to

com.example.drivequickstart, which is what I have in the

API's console.

What I'm going to do next is to set the latest version of

the target SDK.

So we now have devices with the latest version of the SDK.

The Android SDK is 4.2.

So I'm going to have target SDK API 17, Android 4.2 just

to get the latest.

And we're going to compile with same version but with

Google APIs.

Everything else in this dialogue, in this wizard, we

can leave it as it is.

So I'm going to click next.

The next part is about some other

configuration in the project.

You don't need to change anything here if you want to

follow the quickstart.

Of course, when you're writing your application you will have

to change things here maybe.

You can set the icon.

We're going to use the default one.

It doesn't matter.

Then when you have a production app you can change

the icon and all the other things.

And we're going to create a blind activity.

Remember everything in Android starts from an activity.

And this activity is going to be called with a default name

which is main activity.

Its fine with me.

Remember, whenever you want to write your own production

application you can change it.

You probably have to change these values.

So I click finish and the basic skeleton of my

application is created.

And this is how the application would look like,

but we will see later.

We're not going to show this page a lot.

So what this is the application going to do?

This application is going to fire up the camera, the device

camera, allow users to take photos, and whenever a photo

is taken it will be automatically uploaded to

Google Drive.

And that's very easy.

So let me show you how to do it.

So the next thing we have to do is to add the drive API to

the project.

We have a Java client library that can be used.

And the easiest way to add all the required .jars is to use